From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20817 invoked by uid 1002); 23 Jul 2003 19:47:39 -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 9197 invoked from network); 23 Jul 2003 19:47:39 -0000 Date: Wed, 23 Jul 2003 13:46:23 +0600 To: gentoo-dev@gentoo.org Message-ID: <20030723074623.GO19204@fuerzag.ulatina.ac.cr> Mail-Followup-To: gentoo-dev@gentoo.org References: <20030723121603.11ab807e.frogger@gentoo.org> <20030723071005.GN19204@fuerzag.ulatina.ac.cr> <1058987766.3579.14.camel@vertigo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1058987766.3579.14.camel@vertigo> User-Agent: Mutt/1.3.28i From: fede2@fuerzag.ulatina.ac.cr (Alvaro Figueroa Cabezas) Subject: Re: [gentoo-dev] Where to put prerelease vanilla kernels? X-Archives-Salt: 57a7198e-13f7-4153-93e1-d9536914824d X-Archives-Hash: f3db605838252d05ccea1a23edf4b179 On Jul 23 15:16, Chris Gianelloni wrote: > Well, 2.4.22_pre1 is newer than 2.4.21, however, 2.4.21 is the latest > stable kernel from kernel.org. Portage would see 2.4.22_pre1 as newer > and would merge it rather than 2.4.21 when someone installed > vanilla-sources. The only effective way to separate them is to have > them in a separate container. But the policy clearly states that it will be calculated as a lower version. Quote: "Any of these suffixes may be immediately followed by a non-zero positive integer, e.g., linux-2.4.0_pre10. Assuming identical version parts, the suffixes are ordered as follows (lower means older): _alpha < _beta < _pre < _rc < (nosuffix) < _p" -- Alvaro Figueroa -- gentoo-dev@gentoo.org mailing list