On Sunday 31 March 2013 05:19:58 Duncan wrote:
> Mike Frysinger posted on Sun, 31 Mar 2013 01:59:52 -0400 as excerpted:
> > it'd be simpler if we just dropped [texinfo] altogether from @system.
> > if people want `info`, they can `emerge` it themselves. if packages
> > want `makeinfo`, they can DE
On 31/03/2013 16:59, Mike Frysinger wrote:
one option would be to make the makeinfo stuff into a USE flag so all the perl
junk isn't pulled in by default. only the packages that actually generate
info pages can DEPEND on that.
it'd be simpler if we just dropped it altogether from @system. if
On 03/31/2013 06:19 AM, Ulrich Mueller wrote:
>> On Sun, 31 Mar 2013, Duncan wrote:
>
>> Or maybe your intent was to either kill these deps or put them
>> behind USE=doc as well?
>
> USE=doc doesn't look right for this, as it's normally used for large
> sized documentation. Something like US
> On Sun, 31 Mar 2013, Duncan wrote:
> Or maybe your intent was to either kill these deps or put them
> behind USE=doc as well?
USE=doc doesn't look right for this, as it's normally used for large
sized documentation. Something like USE=info might be better.
Ulrich
Mike Frysinger posted on Sun, 31 Mar 2013 01:59:52 -0400 as excerpted:
> it'd be simpler if we just dropped [texinfo] altogether from @system.
> if people want `info`, they can `emerge` it themselves. if packages
> want `makeinfo`, they can DEPEND on it -- few fall into this category
> (<100 by
