Summary: | IUSE needs to be listed as mandatory in variables table | ||
---|---|---|---|
Product: | [OLD] Docs-developer | Reporter: | Alastair Tse (RETIRED) <liquidx> |
Component: | Developers HOWTO | Assignee: | Sven Vermeulen (RETIRED) <swift> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | docs-team |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://www.gentoo.org/doc/en/gentoo-howto.xml | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alastair Tse (RETIRED)
2003-11-22 13:27:48 UTC
actually it was never listed in the policy as being required perhaps the bug is that people think that it is always optional ... it is required if USE flags are used in the ebuild, but not if there are no USE flags used ... i'm pretty certain that it was listed as required. i intepreted that IUSE was mandatory because it says you have to set it even if you don't use and USE flags. this is what was in revision 1.13 <tr><ti><c>IUSE</c></ti><ti>This is set to what USE variables your package uses. If your package uses none, you must set it to <c>IUSE="" </c>. </ti></tr> it was listed in the howto as mandatory not the policy ;) i thought the document was policy? :) but now the document has changed, so that implies policy has changed .. so who decides on these policies then? can i still go and bother people about not putting IUSE in their ebuilds, or should I start removing IUSE="" from mine? personally i always removed IUSE="" from my ebuilds ... i see it as cruft ;) perhaps a discussion needs to be brought up on gentoo-dev about it Was there any consensus on this in the discussion? Some postings tell that IUSE="" is what should be used, another sais that IUSE shouldn't be set in those situations... i think the resolution is that it is mandatory, as nothing has changed in "policy" since revision 1.13 as i posted below. therefore, i think IUSE should be marked as mandatory. Okay, I've set it to mandatory again. If it was optional, then this doesn't harm :) |