Mark Knecht posted on Thu, 27 Aug 2009 09:25:01 -0700 as excerpted: > If it see this it would automatically moved a copy of ebuilds and > distfiles into some sort of a local 'in-use' overlay so they'd still be > available to me on this machine. With something like that at least then > nothing would be lost. Maybe then there's a little app to allow me to > remove it from the overlay when I'm done wit it, or I'd do it by hand. > > What I dislike about the current system is some person out there in the > ether deciding what's right for my hardware with the main criteria being > what's easy for him. Yes, I can, by hand and with time and training, > eventually find and replace things I need, but I have never thought the > way it is working now was the right way.
You're aware that you have a copy of the existing installed ebuild in the portage installed-packages database (typically /var/db/portage), right? That also contains a copy of the environment used to install the package as well, so all the eclasses as they were at installation, etc, tho it'd be a bit of work to reconstruct that. And I'm not sure about the patches if any were applied. But the ebuild, that's easy, and that's the most frequently needed bit. For those with FEATURES=buildpkg, the ebuild is also glued to the end of the tarball containing the built binaries. I happened to discover that before I did the /var/db/portage database, and used an editor to grab the ebuild out of the binpkg a couple of times. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
