From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gratuitous useflaggery (doc and examples)
Date: Sat, 4 Mar 2006 20:20:44 +0200 [thread overview]
Message-ID: <200603042020.56701.danarmak@gentoo.org> (raw)
In-Reply-To: <200603041700.45523.carlo@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
On Saturday 04 March 2006 18:00, Carsten Lohrke wrote:
> On Saturday 04 March 2006 16:43, Dan Armak wrote:
> > If you're concerned about diskspace you can filter out /usr/share/doc
> > entirely, so users do have the choice. The problem here is that the docs
> > USE flag is off by default. Making more packages use the flag would
> > install less docs. Has anyone actually complained that too many docs are
> > installed by default? It's true that some users/situations don't need
> > them, but most do, especially as long as we don't have separate server
> > profiles.
>
> I have seen quite a few bugs about that and actually have filed one¹,
> rotting in bugzilla, myself. I definitely do not care about a few hundred
> KB documentation per ebuild, but some install a lot of documentation and
> accumulated it's a lot of wasted space. Filtering out /usr/share/doc as a
> whole is no choice, when you usually want it, but a fair share not.
I agree that really large docs should be made USE-dependant. This is also
consistent with Ciaran's orig post.
--
Dan Armak
Gentoo Linux developer (KDE)
Public GPG key: http://dev.gentoo.org/~danarmak/danarmak-gpg-public.key
Fingerprint: DD70 DBF9 E3D4 6CB9 2FDD 0069 508D 9143 8D5F 8951
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-03-04 18:21 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-04 1:04 [gentoo-dev] Gratuitous useflaggery (doc and examples) Ciaran McCreesh
2006-03-04 15:15 ` Stuart Herbert
2006-03-04 15:43 ` Dan Armak
2006-03-04 16:00 ` Carsten Lohrke
2006-03-04 18:20 ` Dan Armak [this message]
2006-03-06 16:39 ` Paul de Vrieze
2006-03-06 21:01 ` Carsten Lohrke
2006-03-06 21:11 ` Alec Warner
2006-03-04 16:03 ` Harald van Dijk
2006-03-04 15:56 ` [gentoo-dev] " MIkey
2006-03-04 17:02 ` Ferris McCormick
2006-03-04 18:04 ` [gentoo-dev] " MIkey
2006-03-04 18:13 ` Ciaran McCreesh
2006-03-04 18:18 ` [gentoo-dev] " MIkey
2006-03-04 21:05 ` Duncan
2006-03-04 21:47 ` Thomas de Grenier de Latour
2006-03-04 22:04 ` Simon Stelling
2006-03-04 22:28 ` Thomas de Grenier de Latour
2006-03-05 18:47 ` Mike Frysinger
2006-03-05 19:53 ` [gentoo-dev] " MIkey
2006-03-05 19:57 ` Jan Kundrát
2006-03-05 20:10 ` Mike Frysinger
2006-03-05 20:35 ` [gentoo-dev] " MIkey
2006-03-05 22:11 ` Ferris McCormick
2006-03-05 22:38 ` [gentoo-dev] " MIkey
2006-03-05 22:42 ` [gentoo-dev] " John Mylchreest
2006-03-06 0:09 ` [gentoo-dev] Re: Re: Re: Re: " Mike Frysinger
2006-03-06 16:45 ` Paul de Vrieze
2006-03-06 17:11 ` [gentoo-dev] " MIkey
2006-03-06 20:09 ` [gentoo-dev] " Paul de Vrieze
2006-03-05 22:34 ` [gentoo-dev] Re: Re: Re: Re: " Edward Catmur
2006-03-04 19:24 ` [gentoo-dev] " Ferris McCormick
2006-03-04 19:45 ` [gentoo-dev] " MIkey
2006-03-04 20:47 ` Ferris McCormick
2006-03-05 13:16 ` Patrick Börjesson
2006-03-05 14:52 ` Ned Ludd
2006-03-04 16:37 ` [gentoo-dev] " Duncan
2006-03-04 16:02 ` [gentoo-dev] " Carsten Lohrke
2006-03-06 16:49 ` Paul de Vrieze
2006-03-06 21:08 ` Carsten Lohrke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200603042020.56701.danarmak@gentoo.org \
--to=danarmak@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox