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 1EpSKs-0003Xb-2j for garchives@archives.gentoo.org; Thu, 22 Dec 2005 15:26:30 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jBMFPkYD031988; Thu, 22 Dec 2005 15:25: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 jBMFNuMm016595 for ; Thu, 22 Dec 2005 15:23:57 GMT Received: from c-67-171-150-177.hsd1.or.comcast.net ([67.171.150.177] helo=[192.168.1.106]) by smtp.gentoo.org with esmtpa (Exim 4.54) id 1EpSIO-0000kH-E9 for gentoo-dev@lists.gentoo.org; Thu, 22 Dec 2005 15:23:56 +0000 Message-ID: <43AAC50B.5050003@gentoo.org> Date: Thu, 22 Dec 2005 07:23:55 -0800 From: Donnie Berkholz User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051219) X-Accept-Language: en-us, en 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 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Annoying X.Org tarball naming (and how to deal with it) References: <43AA3AF6.6000903@gentoo.org> <1135264672.28425.6.camel@polylepis.inforead.com> In-Reply-To: <1135264672.28425.6.camel@polylepis.inforead.com> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: beb7558a-6a9d-4ac2-bca7-642dede079d5 X-Archives-Hash: 7b4046c6c4ab04c8d0d610b611983a28 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ferris McCormick wrote: | On Wed, 2005-12-21 at 21:34 -0800, Donnie Berkholz wrote: | 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. | | Please give me your input on this. | | |> Seems fine to me. I hope you are right in your assumption about |> packages in full releases. Even if I'm wrong, it's a matter of setting a single variable, and it will always have to be set for all non-7.0 releases either way (assuming ~ I'd default to 7.0) so they know which release they're part of. Thanks, Donnie -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDqsULXVaO67S1rtsRAo67AKCJ3f5HARANAoYdmKmD50aBMRZowgCeLggq 6Bab1dfkAH7OhpxleZiYZIQ= =88ec -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list