public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeroen Roovers <jer@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: deprecate /usr/share/doc/$PF
Date: Mon, 19 Dec 2011 12:48:54 +0100	[thread overview]
Message-ID: <20111219124854.32502108@epia.jer-c2.orkz.net> (raw)
In-Reply-To: <1324272695.12311.134.camel@rook>

On Mon, 19 Dec 2011 00:31:35 -0500
Alexandre Rostovtsev <tetromino@gentoo.org> wrote:

> On Mon, 2011-12-19 at 03:41 +0100, Jeroen Roovers wrote:
> > For completeness, could you post a list of packages that would
> > benefit from your proposed changes? It's a little thing called
> > scope. :)
> 
> I cannot provide you the full list; for that I would have to rebuild
> the full tree with USE=doc enabled, and I enable it only for a small
> number of packages. But I can give you the packages that I have
> installed on my system right now that install a nontrivial set of
> documentation files in /usr/share/doc/$PF, files that are worth
> bookmarking and would benefit from a location that doesn't change on
> every revision or version bump:

I understand you use some kind of graphical file manager that opens
files for you into some kind of "document viewer". I wouldn't think
anyone tab-completing this on a command line would ever have the need to
"bookmark" stuff otherwise.

> [...]

That's rather a long list. I expected a much shorter list of packages
that use /usr/share/doc/$PF to store data that is read at run time
(which they probably shouldn't do in the first place) so they would
benefit from this. I was not asking for a list of packages that install
documentation in /usr/share/doc/$PF. If that was the only criterium that
mattered, then I wouldn't have asked for a list. :)


     jer



  reply	other threads:[~2011-12-19 11:49 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-18 21:49 [gentoo-dev] RFC: deprecate /usr/share/doc/$PF Alexandre Rostovtsev
2011-12-18 22:02 ` Michał Górny
2011-12-18 23:07   ` Pacho Ramos
2011-12-19  8:31     ` Michał Górny
2011-12-19 10:47       ` Pacho Ramos
2011-12-19  2:26   ` Alexandre Rostovtsev
2011-12-19  2:41     ` Jeroen Roovers
2011-12-19  5:31       ` Alexandre Rostovtsev
2011-12-19 11:48         ` Jeroen Roovers [this message]
2011-12-18 22:07 ` Chí-Thanh Christopher Nguyễn
2011-12-19  0:56   ` Alexandre Rostovtsev
2011-12-19  0:08 ` Ulrich Mueller
2011-12-19  1:52   ` Alexandre Rostovtsev
2011-12-19  4:23     ` Ulrich Mueller
2011-12-19  4:48       ` Dale
2011-12-19 13:29         ` [gentoo-dev] " Duncan
2011-12-19  6:41       ` [gentoo-dev] " Alexandre Rostovtsev
2011-12-19  8:23         ` Ulrich Mueller
2011-12-19 13:51           ` [gentoo-dev] " Duncan
2011-12-19  9:02         ` [gentoo-dev] " Michał Górny
2011-12-19  9:03           ` Ciaran McCreesh
2011-12-19  8:35       ` Michał Górny
2011-12-19 10:08       ` Stelian Ionescu
2011-12-21  1:44     ` Maciej Mrozowski
2011-12-21  3:40       ` Mike Frysinger
2011-12-27 17:29         ` Maciej Mrozowski
2012-01-18 11:12           ` Mike Frysinger
2011-12-27 17:39 ` Andreas K. Huettel

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=20111219124854.32502108@epia.jer-c2.orkz.net \
    --to=jer@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