From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LXyIS-00015R-Qv for garchives@archives.gentoo.org; Fri, 13 Feb 2009 13:41:37 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5F4DEE02B8; Fri, 13 Feb 2009 13:41:34 +0000 (UTC) Received: from smtprelay10.ispgateway.de (smtprelay10.ispgateway.de [80.67.29.24]) by pigeon.gentoo.org (Postfix) with ESMTP id 167DAE02B8 for ; Fri, 13 Feb 2009 13:41:34 +0000 (UTC) Received: from [80.134.62.111] (helo=arkane.local) by smtprelay10.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1LXyIO-00020C-Mt for gentoo-council@lists.gentoo.org; Fri, 13 Feb 2009 14:41:32 +0100 Received: by arkane.local (Postfix, from userid 1000) id B3E84A305; Fri, 13 Feb 2009 14:40:39 +0100 (CET) Date: Fri, 13 Feb 2009 14:40:39 +0100 From: Torsten Veller To: gentoo-council@lists.gentoo.org Subject: [gentoo-council] Re: prepalldocs Message-ID: <20090213140259.TAd9f00.tv@veller.net> Mail-Followup-To: gentoo-council@lists.gentoo.org References: <20090212214925.GA21532@dodo.hsd1.nj.comcast.net> <20090213124130.TAfe8a6.tv@veller.net> <49956364.3050000@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-council@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <49956364.3050000@gentoo.org> Jabber-ID: tove@jabber.ccc.de X-PGP-Fingerprint: 0416 3C11 8D79 65B9 AAD0 2065 BBC7 14D1 9C67 CD96 User-Agent: Mutt/1.5.19 (2009-01-27) X-Df-Sender: 1067115 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 395cb468-20a5-418b-bfdf-e630eea04201 X-Archives-Hash: d86503304652309f54f4a7236aafe6e8 * Petteri R=E4ty : > Torsten Veller wrote: > > * Thomas Anderson : > >> Technical Issues: > >> - Prepalldocs > >> Should the 'prepalldocs' be allowed in current EAPIs? > >> > >> Conclusion: > >> Prepalldocs is banned in current EAPIs(0,1,2). It should= be > >> removed from ebuilds. Petteri R=E4ty(Betelgeuse) will ma= ke QA > >> checks for repoman. > >=20 > > You only did half of your job. > >=20 > > Do we want some docs being compressed, others not? > > Do we want to have compressed docs at all? > > What do you expect from maintainers now? > >=20 > > To me it means: Instead of using prepalldocs I will move the docdir t= o > > a temporary place and dodoc every file back to docdir. Insane. > > Maybe I add a function named prepalldocs to the ebuilds that does the= job. > >=20 > > Thanks. >=20 > Please read the logs. | 15:35 < dev-zero> prepalldocs should be kept internal and usage should = be avoided | 15:36 < dev-zero> reason: internal function and change of it's implemen= tation prooves it | 15:36 < dev-zero> if someone want's it's functionality he should propos= e a solution for a future eapi It is not an internal function. And it's a strange way to prove anything. Around 250 ebuilds use it. So there is probably someone who actually uses= this functionality. > prepalldocs has no clearly defined behavior so it should not be used > by ebuilds. It was possible to rectify it. You chose to remove the function completel= y. > Maintainers should use the public APIs available to them. It's in ebuild.5 for years. And as recruiting lead you probably know that the Developer Handbook cont= ains it as well . > If they have a justified need beyond those, they should open a request > for adding needed things to the next EAPI. I will probably do it after i got answers to the questions above. Thanks.