Brian Harring wrote: > [...] and write an ebuild [...] I'm thinking in terms of making things as easy as possible. I'd rather not have to go to the effort of writing an ebuild for every package (and maybe some of its deps) that I want to hack on.
> If > you're after basically having the unpack func switchable (are we cvs > based, or are we working from a known tarball)... yeah, eww. :) Yep - it's probably not going to be a clean solution, at least for now. But if I can get something that vaguely works then it will be a big timesaver. In the example I used there, we already have the ebuild code designed to build the sources and install the package. And I have the code right here on my disk. I'd like it to be possible to combine the two with minimum effort involved. The switching-source thing was just one example. Here's a couple of other things that have crossed my mind: - I'm manually configuring a package that I want installed in ebuild-fashion. I know when an ebuild runs econf it passes many configure parameters to achieve this (installation into /var/tmp, etc.). It would be nice if I could just run "econf" from the command line and still achieve this. Similarly for emake. Then I can somehow tell portage I've done src_unpack and src_compile manually, so I'd just like it to get on from src_install onwards. - I've just compiled/installed a package from an ebuild in a semi-automatic fashion. I made a mistake in one of the functions. I change one line of code which is an obvious fix. I now want that to take effect on my live filesystem, so I want to recompile (without re-running ./configure as that would slow me down) only the bits that have changed (ala make) and then reinstall. -- [email protected] mailing list
