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 1RcSw9-0003Se-C7 for garchives@archives.gentoo.org; Mon, 19 Dec 2011 02:26:45 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2CE8221C38E; Mon, 19 Dec 2011 02:26:36 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 919A121C25C for ; Mon, 19 Dec 2011 02:26:10 +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 D746A1B400D for ; Mon, 19 Dec 2011 02:26:09 +0000 (UTC) Message-ID: <1324261568.12311.104.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 21:26:08 -0500 In-Reply-To: <20111218230205.4df86707@pomiocik.lan> References: <20111218230205.4df86707@pomiocik.lan> 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: b774c834-acb6-4e64-a9e9-dae193133419 X-Archives-Hash: 574b4e2b036d3638bd2ec92654f2110b On Sun, 2011-12-18 at 23:02 +0100, Micha=C5=82 G=C3=B3rny wrote: > What if 'foo' has slot named 'bar', and there is unslotted 'foo-bar' > package? :P There are no such examples in the tree. The only ebuilds I could find with non-numeric slots are various kernel sources, chromium, google-chrome, beautifulsoup, python-dateutil, b43-firmware, binutils-apple, gcc-apple, and rep-gtk. If cross-compiling there is also insight, gdb, newlib, and uclibc, maybe a few more packages from sys-devel/. For completeness, I suppose that it wouldn't hurt to add a provision to allow package maintainers to choose a different documentation directory if that's required to prevent a file collision. > > Q5: Then why allow package maintainers to alternatively use > > $CATEGORY/$PN-0? A5: Why not? It will not hurt anything, will not > > cause file collisions, and some maintainers of a multislotted > > package, one of which is 0, might prefer to install that slot's docs > > in $CATEGORY/$PN-0 to prevent a potential impression that docs in > > $CATEGORY/$PN apply to all of that package's slots. >=20 > This will make the policy less clear, and documentation locations more > enigmatic for users. Fair point. OK, let's kill the "-0"; slot 0 goes in $CATEGORY/$PN only. > While at this, I think we should somehow move > the docs for all EAPIs to avoid this, and probably move installed ones > as well. >=20 > [...] >=20 > I think some of devs agree we should be allowed to fix past mistakes > without waiting another 20 years till the tree is migrated to a new > EAPI... Then we will also need an eclass-based solution for existing EAPIs to replace dodoc/dohtml. -Alexandre.