From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1EpSF4-00007m-Mx for garchives@archives.gentoo.org; Thu, 22 Dec 2005 15:20:31 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jBMFJk7i020544; Thu, 22 Dec 2005 15:19:46 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jBMFHrk1006853 for ; Thu, 22 Dec 2005 15:17:54 GMT Received: from [216.200.97.58] (helo=polylepis.inforead.com) by smtp.gentoo.org with esmtpa (Exim 4.54) id 1EpSCX-0004pk-Ax for gentoo-dev@lists.gentoo.org; Thu, 22 Dec 2005 15:17:53 +0000 Subject: Re: [gentoo-dev] Annoying X.Org tarball naming (and how to deal with it) From: Ferris McCormick To: gentoo-dev@lists.gentoo.org In-Reply-To: <43AA3AF6.6000903@gentoo.org> References: <43AA3AF6.6000903@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-M3NZB8Qbt6RyX/VurnFs" Date: Thu, 22 Dec 2005 15:17:52 +0000 Message-Id: <1135264672.28425.6.camel@polylepis.inforead.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 X-Archives-Salt: db7a6b5b-b480-44f7-b65e-194e3e52b901 X-Archives-Hash: 01af972023899ca09f97705c180565d9 --=-M3NZB8Qbt6RyX/VurnFs Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2005-12-21 at 21:34 -0800, Donnie Berkholz wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > I'd appreciate some ideas better than what I've come up with so far to > deal with the very strange X.Org release naming. >=20 > When modular tarballs are part of a full X.Org release (7.0, 7.1, etc), > then they are named PN-PV-XORG_RELEASE.tar.(gz|bz2) and S matches. When > modular tarballs are independently released outside a full X.Org > release, they are named the standard way -- PN-PV.tar.(gz|bz2), same for = S. >=20 > Dealing with this all in an automated fashion in x-modular.eclass is > somewhat difficult, and here's what I've come up with: >=20 > A variable (XORG_PV), set by the ebuild, to tell _which_ release it's > part of when it is part of a full release. If it's set, that means (1) > it is part of a full release and (2) indicates which release it's part of= . >=20 > What does this mean for the future? All modular X ebuilds that are part > of a full release will require XORG_PV to be set. All modular X ebuilds > that aren't part of a full release will not require anything new. I'm > doing it this way because I expect there to be more packages that aren't > part of a full release than ones that are. >=20 > Please give me your input on this. Seems fine to me. I hope you are right in your assumption about packages in full releases. >=20 > Thanks, > Donnie > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2 (GNU/Linux) >=20 > iD8DBQFDqjr2XVaO67S1rtsRAhlPAKCMvjj82U6sNPpVYsUOnKOsRwAF4QCgibKM > Ccs1TnSQbXI66BVpf4P8Ed4=3D > =3DNFr1 > -----END PGP SIGNATURE----- --=20 Ferris McCormick (P44646, MI) Developer, Gentoo Linux (Sparc, Devrel) --=-M3NZB8Qbt6RyX/VurnFs Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBDqsOfQa6M3+I///cRAsszAKDUq/n3jgO+I+d6KuhKU92b+qzI2wCg14HU kRpD+ztCHbniDz2/XF5r7EM= =glup -----END PGP SIGNATURE----- --=-M3NZB8Qbt6RyX/VurnFs-- -- gentoo-dev@gentoo.org mailing list