| 1 |
On Wednesday 29 January 2003 09:15 am, Dan Armak wrote: |
| 2 |
> |
| 3 |
> It is not a problem to make an ebuild compile a subset of all available |
| 4 |
> subpackages. <snip> |
| 5 |
> |
| 6 |
> Now the best solution IMHO would be to implement 'subpackages' as i |
| 7 |
> described before. An ebuild could then divide the files it installs into |
| 8 |
> a number of 'subpackages'. If the user requested merging certain |
| 9 |
> subpackages, the ebuild would (should) be smart enough to take only the |
| 10 |
> minimal action required to compile those subpackages. And if the user |
| 11 |
> requested everything (as in an ordinary emerge command), the ebuild |
| 12 |
> would be smart enough not to repeat actions (ie not to run configure |
| 13 |
> more than once). |
| 14 |
> |
| 15 |
|
| 16 |
Thanks Dan. |
| 17 |
|
| 18 |
In the event of a patch of one of the subpackages, you would still need to |
| 19 |
recompile all of the subpackages you want again (instead of just the one |
| 20 |
that has been patched). Is that a correct assumption? |
| 21 |
|
| 22 |
Cheers, |
| 23 |
Dylan Carlson [absinthe@×××××.com] |
| 24 |
|
| 25 |
-- |
| 26 |
gentoo-dev@g.o mailing list |
Archives