| 1 |
On Thu, May 1, 2008 at 5:09 PM, Enrico Weigelt <weigelt@×××××.de> wrote: |
| 2 |
> |
| 3 |
> Hi folks, |
| 4 |
> |
| 5 |
> while building yum, I again ran into trouble because one |
| 6 |
> dependency has to be rebuilt with an specific useflag first |
| 7 |
> (in this case it was libxml2 + python useflag). Actually, |
| 8 |
> there are *lots* of these cases and (AFAIK) portage has no |
| 9 |
> way for properly handling this - it's up to the individual |
| 10 |
> ebuilds to check for those situations and artifically breaking |
| 11 |
> the build. Of coure, breaking builds are ugly. |
| 12 |
|
| 13 |
The proper solution for these cases is implementing USE dependencies, |
| 14 |
which would obsolete pkg_setup checks, and would provide portage with |
| 15 |
info about which USE flags are needed for each dependency. This |
| 16 |
feature is already implemented in other package managers (it's in |
| 17 |
Paludis, maybe in pkgcore too?) and I think we all look forward its |
| 18 |
inclusion in portage. |
| 19 |
|
| 20 |
> My suggestion: make those language bindings being separate |
| 21 |
> packages. So, other packages can depend on them directly, |
| 22 |
> instead of the current, build-breaking hack. |
| 23 |
> |
| 24 |
> I'm not advocating gentoo should do this step alone, but |
| 25 |
> instead join in the upstream and solve it there. |
| 26 |
> |
| 27 |
|
| 28 |
Yes, sometimes it makes sense for upstream to split packages, anyone |
| 29 |
is free to push them for doing so. |
| 30 |
|
| 31 |
Regards, |
| 32 |
|
| 33 |
-- |
| 34 |
Santiago M. Mola |
| 35 |
Jabber ID: cooldwind@×××××.com |
| 36 |
-- |
| 37 |
gentoo-dev@l.g.o mailing list |
Archives