Hi all,
So there have been many complaints about how USE_EXPANDed flags don't belong
in IUSE. There haven't actually been any reasons given though. :P
I've assumed that the reasons they haven't been added thus far are due to what
emerge's output would look like if they were. So I've taken the l
Jason Stubbs wrote:
>So there have been many complaints about how USE_EXPANDed flags don't belong
>in IUSE. There haven't actually been any reasons given though. :P
>
>
>
net-dialup/pppconfig-2.3.11-r1 depends on LINGUAS, but the list of
supported languages is created in pkg_unpack, based on wh
On Sun, Jun 19, 2005 at 07:48:27PM +0300, Alin Nastac wrote:
> Jason Stubbs wrote:
>
> >So there have been many complaints about how USE_EXPANDed flags don't belong
> >in IUSE. There haven't actually been any reasons given though. :P
> net-dialup/pppconfig-2.3.11-r1 depends on LINGUAS, but the li
On Monday 20 June 2005 01:48, Alin Nastac wrote:
> Jason Stubbs wrote:
> > So there have been many complaints about how USE_EXPANDed flags don't
> > belong in IUSE. There haven't actually been any reasons given though. :P
>
> net-dialup/pppconfig-2.3.11-r1 depends on LINGUAS, but the list of
> supp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Stubbs wrote:
> FRITZCAPI_CARDS FCDSL_CARDS VIDEO_CARDS INPUT_DEVICES LINGUAS
>
> Do any of these not follow the same pattern of empty var == all installed?
> Any
> objections to making that a requirement for adding a new USE_EXPAND variable?
Jason Stubbs wrote:
>On Monday 20 June 2005 01:48, Alin Nastac wrote:
>
>
>>net-dialup/pppconfig-2.3.11-r1 depends on LINGUAS, but the list of
>>supported languages is created in pkg_unpack, based on what tarball
>>contains.
>>
>>
>
>What happened to determinism and predictability? From the
On Tuesday 21 June 2005 14:35, Alin Nastac wrote:
> I don't really understand why you consider pppconfig unpredictable.
> the ebuild displays what languages will be installed.
Because there is no way to foretell what will be installed without actually
initiating an install.
> > >The IUSE thing w
On Wednesday 22 June 2005 05:28, Jason Stubbs wrote:
> On Tuesday 21 June 2005 14:35, Alin Nastac wrote:
> > This would be fine as long as LINGUAS do not appear in IUSE. When
> > LINGUAS var is empty, the "equery uses" report would be an abomination .
>
> The whole point is to add this stuff to IUS
On Tuesday 21 June 2005 14:11, Donnie Berkholz wrote:
> Jason Stubbs wrote:
> > FRITZCAPI_CARDS FCDSL_CARDS VIDEO_CARDS INPUT_DEVICES LINGUAS
> >
> > Do any of these not follow the same pattern of empty var == all
> > installed? Any objections to making that a requirement for adding a new
> > USE_E
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Stubbs wrote:
> Any reason why INPUT_DEVICES is needed in USE_EXPAND rather than just as
> local
> USE flags? It's kind of the odd one out among the above.
The reasoning for that is that hardware support doesn't make sense as
USE flags, so it
Donnie Berkholz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Stubbs wrote:
Any reason why INPUT_DEVICES is needed in USE_EXPAND rather than just as local
USE flags? It's kind of the odd one out among the above.
The reasoning for that is that hardware support doesn't make sens
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alec Warner wrote:
> Donnie Berkholz wrote:
> The reasoning for that is that hardware support doesn't make sense as
> USE flags, so it should be something else. In this case, that was
> INPUT_DEVICES. We haven't been able to take much advantage of it y
On Wednesday 22 June 2005 02:07, Donnie Berkholz wrote:
> Alec Warner wrote:
> > Donnie Berkholz wrote:
> > The reasoning for that is that hardware support doesn't make sense as
> > USE flags, so it should be something else. In this case, that was
> > INPUT_DEVICES. We haven't been able to take muc
13 matches
Mail list logo
