From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29384 invoked by uid 1002); 24 Jul 2003 09:07:15 -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 25850 invoked from network); 24 Jul 2003 09:07:14 -0000 Date: Thu, 24 Jul 2003 18:07:11 +0900 To: gentoo-dev@gentoo.org Message-ID: <20030724090711.GH30147%chutz@gg3.net> References: <20030723121603.11ab807e.frogger@gentoo.org> <20030724082857.GB980@Dimosys.mech.kuleuven.ac.be> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline In-Reply-To: <20030724082857.GB980@Dimosys.mech.kuleuven.ac.be> User-Agent: Mutt/1.5.4i-ja.1 From: Georgi Georgiev Mail-Followup-To: gentoo-dev@gentoo.org X-Delivery-Agent: TMDA/0.80 (Determine) X-Primary-Address: chutz@gg3.net Reply-To: Georgi Georgiev Subject: Re: [gentoo-dev] Where to put prerelease vanilla kernels? X-Archives-Salt: d447ee6b-9c51-4033-9439-e07e2647097f X-Archives-Hash: 8c4077863f9fa87b4ee10e44c86c61a1 --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 24/07/2003 at 10:28:57(+0200), Sven Vermeulen used 1.6K just to say: > 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 >=20 > Its more like the testing. ~arch is when a developer deems his package re= ady > for inclusion.=20 >=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. >=20 > 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, peop= le > which are using pre-vanilla-sources will be stuck at the latest _pre (or > _testing). >=20 > And when they emerge the vanilla-sources, they'll miss the next _pre cycl= e. > =20 > Personally, I would go for package.mask Wow... I was getting scared seeing how this thread developed, but in the en= d, after reading this post, I realized that the world has not gone *completely* mad, after all. I fully support the opinions stated above, and I simply cannot comprehend w= hat the big deal with ~arch masking vanilla-sources is. Even *considering* the option of a separate package is ridiculous. As long as developers are caref= ul enough to not remove the ~arch mask from any _pre kernel, I am perfectly fi= ne, and I believe there wouldn't be anyone who isn't fine. What are we trying t= o do -- make sure people who insist on running the *unstable* profile actually d= on't get the "unstable" sources. There is also the package.mask if you feel that= is not enough, but this was also mentioned already. And the decision that was taken is ... weird. What is the idea in having unstable (i.e. ~masked) packages in the first place? Are you going to keep only stable versions in vanilla-sources? What's the point? Why not move all _pre, _alpha ane _beta versions of packages in separate directories? As it was already mentioned, = _pre kernels are more stable than many other packages. The first one I can think= of is gentoo-sources, that insisted on corrupting my filesystem every now and then, so I couldn't upgrade my glibc, without upgrading to vanilla-sources first (some files were having funny contents during compilation but it was = hard to reproduce), and I am running vanilla-sources ever since. Sorry for the tone, but I feel frustrated. --=20 () Georgi Georgiev () A committee is a life form with six or more () () chutz@gg3.net () legs and no brain. -- Lazarus Long, "Time () () +81(90)6266-1163 () Enough For Love" () --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/H6G/fXO2NUT1EmYRAj0+AKDmt4qE86jF0Fz4yPPKESbVMJQhrgCgnizN mzt5DEa4OXX79rUVjQKwBgE= =tqSz -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm--