I think, that USE flags should appear only in one file, shouldn't they? Found USE flag 'wavelan' in use.desc and use.local.desc Haven't checked others. There may be more conflicts... Reproducible: Always Steps to Reproduce:
Would a repoman check be good for this? Do it and report it for any use flag in IUSE...
I'd love to see a repoman check for this.
There was the idea floating around to put "better" use flag descriptions in use.local.desc for global flags, see the "USE flags" thread on gentoo-dev from March. So far no "official" decision (whatever that means), so I'm against a repoman check for now.
Hmmm... just started the following command find /usr/portage -name "*.ebuild" -exec grep -H -i wavelan {} \; and couldn't find any ebuild having wavelan in IUSE... I'm not familiar with repoman. Started it for the whole portage tree, but had to stop it after two hours. Will try it again tomorrow if necessary.
Created attachment 56323 [details] ShellScript for detecting doubled use flags I checked all use flags and found that many use flags appear in both description files. Run the script and see for yourself.
To summarize the thread that Marius referred to, the idea is that use.desc descriptions are often too generic in relation to some packages and that use.local.desc could be used to better specify how the use flag relates to those specific packages where necessary. Presently, there are no tools that support this (at least intentionally) but supporting it seems like a good idea, it won't break anything and there's no official policy (that I know of) that it is contrary to. WONTFIX?
*** Bug 89979 has been marked as a duplicate of this bug. ***
Created attachment 56884 [details] Simple script who explain use with emerge -pv pkg | script Not very clean, but a good idea to start for the script discuted in commentaries
Also, i think that it is not a good idea to put the use flag description per packages in use.local.desc as Marius Mauch propose. I think it is better to put it in the ebuild, or a separated file by the package's (modifier, owner..). Because of this, when a package will be updated, the use flags description will be too and doesn't need a use.local.desc update.
This all sounds closely related to bug #84884, where there is some code that makes emerge and equery display this special flags descriptions. It provides a small API that would make it very easy to add checks in repoman too.
Well, I removed all the duplicates where it made sense to. Having portage handle use descriptions differently is an entirely different bug.
