public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: tetromino@gentoo.org
Subject: Re: [gentoo-dev] RFC: deprecate /usr/share/doc/$PF
Date: Mon, 19 Dec 2011 10:02:07 +0100	[thread overview]
Message-ID: <20111219100207.0a109cc1@pomiocik.lan> (raw)
In-Reply-To: <1324276860.12311.177.camel@rook>

[-- Attachment #1: Type: text/plain, Size: 2091 bytes --]

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

> Using /usr/share/doc/$PN-$SLOT with exceptions for packages that have
> the same ($PN, $SLOT) but different categories would not scale: it
> turns out there are >100 of them in the main tree.

And I hope there will be more. We should seriously start splitting
packages rather than using old Gentoo bloat like IUSE='perl python
foobar foobaz'.

> Fortunately, there *is* a neat solution.
> 
> Symlinks.

Symlinks are never neat. In this particular case, they just mean
someone has failed horribly and now is hoping to fix it taking
the path of least resistance.

> > 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.
> 
> You are correct that categories are Gentoo-specific and are therefore
> not ideal for installed paths. However, for generating a stable path
> to documentation files, one that does not shift on version bumps and
> revbumps, there doesn't seem to be any alternative.

To be honest, the whole ${PF} is Gentoo-specific. Package names not
necessarily follow upstream ones; sometimes we need to change versions
as well to match ${PV} semantics or logic. Perl modules are quite
a large case here.

Sometimes packages in different categories collide. Right now, devs
have to be aware not to install colliding docs -- usually through
renaming files. Using category will at least partially fix this.

Shifting is unavoidable. SLOTs can change, categories can change,
package names can change. Of course, all the mentioned cases are much
rarer than PF changing but -- as pointed out before -- these could
change without reinstalling packages.

If we decided to use such names, the most correct approach would be to
have PM handle docmoves as well. But -- on the other hand -- there will
be always some hardwired paths which will be updated only on real
package rebuild...

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

  parent reply	other threads:[~2011-12-19  9:01 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
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         ` Michał Górny [this message]
2011-12-19  9:03           ` [gentoo-dev] " 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=20111219100207.0a109cc1@pomiocik.lan \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=tetromino@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