public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexandre Rostovtsev <tetromino@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: deprecate /usr/share/doc/$PF
Date: Sun, 18 Dec 2011 19:56:58 -0500	[thread overview]
Message-ID: <1324256218.12311.47.camel@rook> (raw)
In-Reply-To: <4EEE6420.3050702@gentoo.org>

On Sun, 2011-12-18 at 23:07 +0100, Chí-Thanh Christopher Nguyễn wrote:
> Alexandre Rostovtsev schrieb:
> > Answers to anticipated questions:
> Q8: SLOT can change after the package was installed. How to handle this
> case?

I think the slotmove should happen without renaming the documentation
directory; silently moving installed files after an emerge --sync
without the user's explicit request seems a bad idea.

This means that a slotmove could result in a future file collision. If
foo-1.0 and foo-2.0 were in slot "1", and >=foo-2.0 was slotmoved from
"1" to "2", then if a user had foo-2.0 installed before the slotmove,
attempting to install foo-1.0 after the slotmove would result in a file
collision in /usr/share/doc/*/foo-1. Such collisions would have to be
resolved with the usual technique of revbumps and blockers.

However, in practice slotmoves that could cause such collisions are
infrequent. Among the 94 slotmoves for 2009 and 2010, I see only five
that would have resulted in potential file collisions in /usr/share/doc
under the proposed scheme: ati-drivers, clojure, vala, libchamplain, and
clutter-gtk. Among the several hundred slotmoves for 2011 so far, I see
*zero* that would have resulted in a collision.

It is possible that I missed some, but even then, I think that less than
10% of slotmoves - probably much less - would have been affected.

-Alexandre.




  reply	other threads:[~2011-12-19  0:57 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 [this message]
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=1324256218.12311.47.camel@rook \
    --to=tetromino@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