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 1L6mpk-0004V4-TC for garchives@archives.gentoo.org; Sun, 30 Nov 2008 13:59:37 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3D7C6E0572; Sun, 30 Nov 2008 13:59:35 +0000 (UTC) Received: from mail.metalmail.org (mail.metalmail.org [87.118.103.88]) by pigeon.gentoo.org (Postfix) with ESMTP id 051BEE0572 for ; Sun, 30 Nov 2008 13:59:35 +0000 (UTC) Received: from pluto.atHome (p5498368E.dip0.t-ipconnect.de [84.152.54.142]) by mail.metalmail.org (Postfix) with ESMTP id BDB3FD880CE for ; Sun, 30 Nov 2008 14:59:37 +0100 (CET) Received: by pluto.atHome (sSMTP sendmail emulation); Sun, 30 Nov 2008 14:59:37 +0100 Date: Sun, 30 Nov 2008 14:59:36 +0100 From: Matti Bickel To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [RFC] Moving HOMEPAGE out of ebuilds for the future Message-ID: <20081130135936.GA30029@pluto> References: <200811301446.43234.scarabeus@gentoo.org> 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-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pWyiEgJYm5f9v55/" Content-Disposition: inline In-Reply-To: <200811301446.43234.scarabeus@gentoo.org> User-Agent: Mutt/1.5.16 (2007-06-09) X-Archives-Salt: 2379ef88-e522-4e54-afd0-a50413f48b1f X-Archives-Hash: d139cb4a3337fa8d58ac10ef815d6908 --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Tom=C3=A1=C5=A1 Chv=C3=A1tal wrote: > On Sunday 30 November 2008 14:23:48 Diego 'Flameeyes' Petten=C3=B2 wrote: > > I have a very quick proposal: why don't we move the packages' homepage > > in metadata.xml (since it's usually unique for all the versions) and we > > get rid of the variable for the next EAPI version? > I would rather see something like: >=20 > packagename/metadata.xml > packagename/package-base.ebuild > packagename/packagename-version.ebuild > packagename/Manifest > packagename/Changelog Correct me if i'm wrong, but this doesn't address the problem with multiple versions having multiple homepages. I'm with Diego here that this should be *very* rare. Can somebody verify this? I mean just throw a little shell script on the portage tree showing which ebuilds differ in HOMEPAGE but still have the same path.. my poor ibook would take too long for such a thing, so sorry, no data here. And while your proposal sounds more compliant to the DRY principle, i would object it on the basis that it makes a single ebuild actually harder to understand as you have to read (1) eclasses, (2) -base.ebuild and (3) -version.ebuild. --=20 Regards, Matti Bickel Signed/Encrypted email preferred (key 4849EC6C) --pWyiEgJYm5f9v55/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkkynEgACgkQfNMcoUhJ7GxzAwCeLj6O+ocNn6snevVOpD2Mgw5t 2JsAoKfCEFjNstIYv47LAwP0bKQ3s2fW =PYLL -----END PGP SIGNATURE----- --pWyiEgJYm5f9v55/--