-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mike Frysinger wrote: > On Mon, Nov 07, 2005 at 10:08:45AM -0500, Alec Warner wrote: > >>Mike Frysinger wrote: >> >>>On Mon, Nov 07, 2005 at 02:05:37AM -0500, Alec Warner wrote: >>> >>> >>>>Could we by chance, mandate some sort of comment field in that file not >>>>unlike package.mask? >>> >>> >>>what really needs explanation ? i mean, why do you need a comment for say: >>>aalib media-libs/aalib >>>canna app-i18n/canna >>>and every package in there is the same way >> >>Because I want to know WHY this flag is required to be in use.defaults >>vs a normal flag? Because maybe flags were added in the past to cover >>situation X and now that situation is fixed another way and we can pull >>the flag out of use.defaults > > > i think you're confusing use.defaults with the USE in profile make.defaults > > use.defaults is there to simply automatically enable USE flags if a package > is > installled, nothing more and nothing less > > >>>>I'm also a bit worried that things were placed in there a while ago and >>>>are no longer needed, may also be a good idea to date the entries. >>> >>> >>>like what ? dating is pointless imo, use `cvs ann` :P >> >>Right..cvs ann...how do I do that from viewCVS again? :) > > > well, if i had to guess, i'd say try clicking the link that says '(annotate)' > > >>In the end I just wonder at the use of these things. They are both >>helpful and bad. > > > if you want to start a thread about punting use.defaults, then do it ... > trying to slowly bleed the file of entries is dumb > -mike
I know what use.defaults does. I'm saying that: A. use.defaults exists for a reason, and developers are using it to enable functionality. B. Turning off a flag in use.defaults may cause undesired behavior. If the developed enabled a flag in there, I generally think that the developer knows they are doing, maybe thats a bad assumption? :) If there are no consequences to removing auto-use from USE_ORDER I'll do it ( I do similar things on my lone server ). If I am going to over-ride a flag in use.defaults, I know what it does, but I don't know what it affects. Obviously the flag was added to use.defaults for a reason, either because it's required for something, or it adds value to the system, or something I can't think of ;) I simply want to know what that reason is. If it doesn't do anything useful, then yeah, I'd like to see the flag punted from use.defaults because then it's just fluff. - -Alec Warner (Antarus) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iQIVAwUBQ293tmzglR5RwbyYAQIP4g/+Jw9dOjK619VOmOPyq5LsSwZW3oYZDuWA 6TKu7JBjofefCchsERhRo75N8SHc1keCdoQ1cxdSgy366Gau6H+6TRKzhlP3ls9D Ax7XHN5A2P7F8xz07vRqMoq/u9qAtunhB9wiQKwnUrjUvz+uaYL9O9m+P7BU3aRd k99ds87794Y2JEhJR2u5xz80Yaqe/4Dq7wktm38immIVmF8njKRfq5T1O8jAamBh qlWv/DXllBKvBnFnJlkXSyXLkPN9fOewvEHm++RB2fNjf2wt2sWWRUiXrK/wPmaT t+B2lN86EljsGXbT1AVUHy/3bgeOMGHPL81zAbMHIiEZPIarwkX6g2khm9xVhrJt 3ig3WZxXahV03Mv3PKgdERSHNxuN2b1CXiK+8bSfYUftmZMIs/ddlUXft9kiDTRU H1tc6FjXoxFCtROsThMI8er6NOP0gB5y+O4F6JWq2I0ScwAcb22K8Jjn4XX4KJDI qZhbXTJCLhEV5TTznClAPCSeWRVqKGX1jRZnOXfq+fZ+W7MsAPzphZFYySHyx9dY A74z0UHQJUeJodrJlCWcyFlkd4hgXyLnLJqcMBNJVpMCYj1uh3pYUN8U5AKKNVeR 3N2oNQusTefTzq/IsU3svwQgDmudKBcU8+DhqkjXf4r+J6zxESXt/s5wms7xfPGU D2HwELW0Ojc= =8L7y -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list
