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