On Mon, Nov 07, 2005 at 10:50:14AM -0500, Alec Warner wrote:
> 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.
>
> that reason is. If it doesn't do anything useful, then yeah, I'd lik
-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 tha
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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
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-i18
On Monday 07 November 2005 19:25, Henrik Brix Andersen 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?
>
> Sounds like a really good idea to me. Will this require any
> modific
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?
Sounds like a really good idea to me. Will this require any
modifications to portage, or will it automagically ignore # comments
in that fil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Could we by chance, mandate some sort of comment field in that file not
unlike package.mask?
I usually like to know the reason why these flags are being switched on.
Certainly there are some flags that I don't mind and there are others
where I just ha