| 1 |
On Friday 11 June 2004 21:12, Mike Frysinger wrote: |
| 2 |
> On Friday 11 June 2004 02:17 pm, Paul de Vrieze wrote: |
| 3 |
> > > IUSE isnt defined when portage hits that (it is defined later on) so |
| 4 |
> > > you get the warning message ... portage needs a way to handle |
| 5 |
> > > conditional inherits, so you cant really say the eclass/ebuild is |
| 6 |
> > > broken |
| 7 |
> > |
| 8 |
> > No it doesn't, those eclasses / ebuilds need to be written in such that |
| 9 |
> > there is no need for a conditional use of them. |
| 10 |
> |
| 11 |
> what about packages that optional perl modules ? or optional python modules |
| 12 |
> ? do you propose we duplicate the eclass code in those ebuilds ? |
| 13 |
> pulling in those eclasses pulls in the DEPEND on perl/python which may not |
| 14 |
> be correct if USE="-perl -python" ... |
| 15 |
> -mike |
| 16 |
|
| 17 |
Hmm. That doesn't make it easier does it ;-). What about two eclasses. One |
| 18 |
that accomodates conditional use, and the other which pulls in all the |
| 19 |
automatic dependency mumbojumbo. |
| 20 |
|
| 21 |
Paul |
| 22 |
|
| 23 |
-- |
| 24 |
Paul de Vrieze |
| 25 |
Gentoo Developer |
| 26 |
Mail: pauldv@g.o |
| 27 |
Homepage: http://www.devrieze.net |
Archives