From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31017 invoked by uid 1002); 24 Jul 2003 08:36:00 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 26005 invoked from network); 24 Jul 2003 08:36:00 -0000 Date: Thu, 24 Jul 2003 10:28:57 +0200 From: Sven Vermeulen To: gentoo-dev@gentoo.org Message-ID: <20030724082857.GB980@Dimosys.mech.kuleuven.ac.be> Mail-Followup-To: gentoo-dev@gentoo.org References: <20030723121603.11ab807e.frogger@gentoo.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tjCHc7DPkfUGtrlw" Content-Disposition: inline In-Reply-To: <20030723121603.11ab807e.frogger@gentoo.org> X-Operating-System: Linux 2.4.20 X-Telephone: +32 486 460306 User-Agent: Mutt/1.5.4i Subject: Re: [gentoo-dev] Where to put prerelease vanilla kernels? X-Archives-Salt: f0ebdab4-7cde-4149-9483-d1a5b9f948ec X-Archives-Hash: 9fcf055b65b107c8d1c36bf88e5ab1fc --tjCHc7DPkfUGtrlw Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 23, 2003 at 12:16:03PM -0400, Matt Rickard wrote: > I'm wondering what's the best way to handle these? First option is to > put them in vanilla-sources, for example, > vanilla-sources-2.4.22_pre7.ebuild. If we ~ mask them, people using the > unstable profile will get these prerelease kernels if merging > vanilla-sources. I'm not sure this is desired behavior, however, it IS > the unstable profile :) =20 Its more like the testing. ~arch is when a developer deems his package ready for inclusion.=20 > Another option is to create a separate category for these, something > like pre-vanilla-sources. This has the benefit that people who want > vanilla will get only vanilla, and not a prerelease -- regardless of > which profile they are using. I don't like this idea (even though I'm in the minority here :). First of all, when the _pre's are finished and the stable kernel is released, people which are using pre-vanilla-sources will be stuck at the latest _pre (or _testing). And when they emerge the vanilla-sources, they'll miss the next _pre cycle. =20 Personally, I would go for package.mask Wkr, Sven Vermeulen --=20 Save some animals, eat a vegetarian. --tjCHc7DPkfUGtrlw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/H5jJXfqz7M26L9sRAv7QAJ49sSfIduLs76vfJlUwgKTcxccMlgCdEgxu uHgSlZntHaW7nAJ8+BjsHQ8= =kCG/ -----END PGP SIGNATURE----- --tjCHc7DPkfUGtrlw--