From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RcRXr-0006K8-W7 for garchives@archives.gentoo.org; Mon, 19 Dec 2011 00:57:36 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5305D21C119; Mon, 19 Dec 2011 00:57:27 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 77A1021C0D1 for ; Mon, 19 Dec 2011 00:57:00 +0000 (UTC) Received: from [192.168.1.43] (pool-173-66-233-165.washdc.fios.verizon.net [173.66.233.165]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id BB8131B4003 for ; Mon, 19 Dec 2011 00:56:59 +0000 (UTC) Message-ID: <1324256218.12311.47.camel@rook> Subject: Re: [gentoo-dev] RFC: deprecate /usr/share/doc/$PF From: Alexandre Rostovtsev To: gentoo-dev@lists.gentoo.org Date: Sun, 18 Dec 2011 19:56:58 -0500 In-Reply-To: <4EEE6420.3050702@gentoo.org> References: <4EEE6420.3050702@gentoo.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.2 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 3770c71e-ff39-4993-abf5-c840c8163644 X-Archives-Hash: da3979ad05f4e59879865ca03168c9c4 On Sun, 2011-12-18 at 23:07 +0100, Ch=C3=AD-Thanh Christopher Nguy=E1=BB=85= 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 >=3Dfoo-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.