From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: deprecate /usr/share/doc/$PF
Date: Mon, 19 Dec 2011 05:23:08 +0100 [thread overview]
Message-ID: <20206.48172.238713.183104@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <1324259574.12311.86.camel@rook>
>>>>> On Sun, 18 Dec 2011, Alexandre Rostovtsev wrote:
>> Can we please avoid the bloat of another directory level here?
>> ${CATEGORY}/${PN} will be even longer than ${PF} in most cases.
> The problem is that ($PN, $CATEGORY) pairs are not unique. Think of
> x11-terms/terminal:0 and gnustep-apps/terminal:0, or
> app-misc/beagle:0 and sci-libs/beagle:0, or app-misc/nut:0 and
> sys-power/nut:0. I could not think of any better solution than using
> $CATEGORY/$PN-$SLOT.
Thinking about it a little more, I believe that ${CATEGORY} shouldn't
appear anywhere in the path of installed files, for the following
reasons:
1. Users may not know the category of a package, therefore it's not
obvious for them where to find its documentation. (Think of it from
the perspective of a user on a multiuser system, who didn't install
the packages on that system.) OTOH, the name of the package (PN) is
obvious in most cases, since it will coincide with the upstream
name.
2. It doesn't play well with bash completion. When searching for
documentation of a specific package (and only knowing PN), one can
currently type the pathname up to PN and press tab which will
complete PVR. With CATEGORY _before_ PN this would no longer work.
3. CATEGORY and SLOT are Gentoo specific, related to the way how we
organise our packages. Neither of them should appear in the
directory structure of installed packages. The problems related to
package and slot moves (where CATEGORY or SLOT change) also show
that something is wrong with the approach. (BTW, in the current
system, PR is also Gentoo specific. It doesn't suffer from problems
with package moves though.)
> Do you have a better proposal that does not rely on $PVR?
Leave things as they are. It's not perfect, but IMHO your approach
would create at least as many problems as it would solve.
Alternatively, a minimal solution would be to drop only ${PR}, i.e.
install documentation under /usr/share/doc/${P}.
Ulrich
next prev parent reply other threads:[~2011-12-19 4:23 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
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 [this message]
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=20206.48172.238713.183104@a1i15.kph.uni-mainz.de \
--to=ulm@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