| 1 |
On Tue, 19 Oct 2004 20:40:54 +0200, Dan Armak <danarmak@g.o> wrote: |
| 2 |
> > what gain over DO_NOT_COMPILE does this give? |
| 3 |
> |
| 4 |
> It allows portage to manage interdependencies and, in fact, everything else it |
| 5 |
> manages. Heavy use of DO_NOT_COMPILE, such as emerging only kmail + its deps |
| 6 |
> from all of kdepim (of course each user has to figure out for himself what |
| 7 |
> those deps are, first), is more or less equivalent to linux from scratch. |
| 8 |
> It'd be manual building, except portage will think it knows what is |
| 9 |
> installed, and will be wrong. |
| 10 |
> |
| 11 |
|
| 12 |
over 300 ebuilds more to manage because of a slight gain in user |
| 13 |
friendliness (not even usability)? -- sounds like one of ciaranm's |
| 14 |
satires :) |
| 15 |
|
| 16 |
What about USE="kde-minimal kmail" emerge kdepim? and now that you |
| 17 |
mention dependencies. What about a package that depends on apache |
| 18 |
having gdbm or ipv6 or threads support? |
| 19 |
|
| 20 |
First of all, there is "etcat uses" and if its not convenient enough, |
| 21 |
so what if things will fail with a clear message like kmail missing? |
| 22 |
-- not any different than it is now :) |
| 23 |
|
| 24 |
-- |
| 25 |
gentoo-dev@g.o mailing list |
Archives