| 1 |
On Thursday 07 July 2005 04:49 pm, Aron Griffis wrote: |
| 2 |
> Current (possibly unwritten) policy: |
| 3 |
> |
| 4 |
> - eclasses declare USE-flags they honor in their own IUSE |
| 5 |
> - ebuilds declare USE-flags they honor in their own IUSE |
| 6 |
> - ebuilds do not declare USE-flags honored by eclasses they inherit |
| 7 |
|
| 8 |
err this third one i dont think we do ... eclasses declare their own stuff and |
| 9 |
ebuilds declare their own ... it's a black box like it should be ... |
| 10 |
|
| 11 |
portage was fixed a while ago to trim out duplicated flags in IUSE wasnt it ? |
| 12 |
|
| 13 |
> Of course this assumption is false. An eclass might provide |
| 14 |
> a function "install_docs" that calls, for example, "use doc". The |
| 15 |
> ebuild inheriting the eclass might not call "install_docs". In that |
| 16 |
> case, if IUSE="doc" in the eclass, it will be inaccurately displayed |
| 17 |
> when doing emerge -pv of the package. |
| 18 |
|
| 19 |
does this really come up all that often that it needs to be handled ? seems |
| 20 |
like a lot of effort for little gain ... |
| 21 |
-mike |
| 22 |
-- |
| 23 |
gentoo-dev@g.o mailing list |
Archives