| 1 |
Vapier wrote: [Thu Jul 07 2005, 06:13:06PM EDT] |
| 2 |
> On Thursday 07 July 2005 04:49 pm, Aron Griffis wrote: |
| 3 |
> > Current (possibly unwritten) policy: |
| 4 |
> > |
| 5 |
> > - eclasses declare USE-flags they honor in their own IUSE |
| 6 |
> > - ebuilds declare USE-flags they honor in their own IUSE |
| 7 |
> > - ebuilds do not declare USE-flags honored by eclasses they inherit |
| 8 |
> |
| 9 |
> err this third one i dont think we do ... eclasses declare their own stuff and |
| 10 |
> ebuilds declare their own ... it's a black box like it should be ... |
| 11 |
|
| 12 |
Sorry, my last bullet point was unclear. I meant what you're saying. |
| 13 |
|
| 14 |
> > Of course this assumption is false. An eclass might provide |
| 15 |
> > a function "install_docs" that calls, for example, "use doc". The |
| 16 |
> > ebuild inheriting the eclass might not call "install_docs". In that |
| 17 |
> > case, if IUSE="doc" in the eclass, it will be inaccurately displayed |
| 18 |
> > when doing emerge -pv of the package. |
| 19 |
> |
| 20 |
> does this really come up all that often that it needs to be handled? |
| 21 |
> seems like a lot of effort for little gain ... |
| 22 |
|
| 23 |
You're right... it probably doesn't matter. It's just annoying. |
| 24 |
|
| 25 |
Regards, |
| 26 |
Aron |
| 27 |
|
| 28 |
-- |
| 29 |
Aron Griffis |
| 30 |
Gentoo Linux Developer |
Archives