On Sat, 07 Jun 2008 01:40:36 +0200 Vlastimil Babka <[EMAIL PROTECTED]> wrote: > Doug Goldstein wrote: > > An clearly motivation explanation that I didn't add, which I'm > > going to add once I send this is the fact that as per the QA > > Project, use.local.desc can not contain a USE flag that already > > appears globally in use.desc. This would allow a description for > > that USE flag to be contained in the metadata. > > What reason does the QA Project have to disallow such thing? Is it > just so that package-specific info does not concentrate in one huge > file? Or is it the danger that the meaning of package-specific flags > would drift too far from the global flag's meaning and lead to > confusion? If it's the first, then metadata.xml seems like a good > place. If the latter, then it wouldn't make much sense to approve the > syntax and then disallowing it by QA :)
As I recall, the logic was that global use flags have a single, well defined global meaning. Using use.local.desc for *refinements* wouldn't go against that, but it's a fairly badly defined line. -- Ciaran McCreesh
signature.asc
Description: PGP signature
