[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev] proposed USE flag: nodoc[Message Scanned][Message Scanned]
From:       Drake Wyrm <wyrm () haell ! com>
Date:       2004-01-30 8:37:34
Message-ID: 20040130083734.GB22140 () phaenix ! haell ! com
[Download RAW message or body]


On Fri, Jan 30, 2004 at 02:34:43AM -0500, in
<401A0913.8080108@gentoo.org>, John Davis <zhen@gentoo.org> wrote:
> Drake Wyrm wrote:
> >On Fri, Jan 30, 2004 at 02:05:57AM -0500, in 
> ><401A0255.9010600@gentoo.org>, John Davis <zhen@gentoo.org> wrote:
> >
> >>Drake Wyrm wrote:
> >>
> >>>Just had an idea for a new USE flag. As a companion to the 'doc' USE flag
> >>>(which installs extra documentation), how about a USE flag which inhibits
> >>>/any/ documentation. This would be highly handy for trimming down a 
> >>>system
> >>>such as a server or router which will never have a warm body sitting in
> >>>front of it after everything is installed and configured. What say ye?
> >>Why not put -doc in USE? If the ebuild is specifying docs to install 
> >>using the doc USE, doing the above will negate that effect. All that 
> >>needs to be done is make more ebuilds conform to it.
> >Because nearly every ebuild, even those which USE doc, installs the
> >normal documentation (e.g. manpages, texinfo, </usr/share/doc/${PVR}/*>)
> >even with USE=-doc. USE=doc results in *extra* goodies.
> Then the flag is ambiguous - does it mean all docs or just "special" 
> docs? I say the best way to go is to just make more ebuilds conform, 
> perhaps add more documentation about the doc flag to the portage guide.

What's ambiguous about it?
     doc - Adds extra documentation (API, Javadoc, etc)
  -- use.desc
-- 
Batou: Hey, Major... You ever hear of "human rights"?
Kusanagi: I understand the concept, but I've never seen it in action.
  --Ghost in the Shell

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]