public inbox for gentoo-kernel@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: gentoo-kernel@lists.gentoo.org
Subject: Re: [gentoo-kernel] [ANNOUNCE] genpatches-2.6.16-2 release
Date: Tue, 28 Mar 2006 23:37:15 -0500	[thread overview]
Message-ID: <442A0EFB.1050500@gentoo.org> (raw)
In-Reply-To: <20060328170923.GA21022@osgiliath.brixandersen.dk>

Henrik Brix Andersen wrote:
> On Tue, Mar 28, 2006 at 05:48:13PM +0100, Daniel Drake wrote:
>> John Mylchreest wrote:
>>> Since were bunlding these whole now, should we just start naming the
>>> ebuilds correctly instead?
>> I don't think so. 2 -stable releases in the 2.6.15 cycle didn't have any 
>> immediate corresponding gentoo-sources bump since the patches were 
>> already included. The fact that we include patches alongside -stable 
>> means that using their notation isn't entirely accurate in our situation.
> 
> Both naming schemes have their advantages, but I see more
> disadvantages with using the 2.6.x.y naming scheme in gentoo-sources
> than I see advantages (primarily the reason Daniel stated above).
> 
> I suggest we keep the current naming scheme for gentoo-sources, as it
> seems most correct.
> 
> Regards,
> Brix

fwiw, I've got mips-sources modified to follow the upstream kernel.org notation 
of 2.6.x.y (even though our primary upstream, linux-mips.org, doesn't utilize 
this notation at all).

There's logic in the ebuild that can switch between using -rc, point releases 
(the .y ones) and standard versions, and it modifies the logic to fetch the 
appropriate patch(es) from upstream to save on what we need to upload to the 
gentoo mirrors.

Been following this since ~2.6.12, and we haven't had any issues with the 
versioning in portage or reported from users.  mips-headers even uses it now.


--Kumba

-- 
Gentoo/MIPS Team Lead
Gentoo Foundation Board of Trustees

"Such is oft the course of deeds that move the wheels of the world: small hands 
do them because they must, while the eyes of the great are elsewhere."  --Elrond
-- 
gentoo-kernel@gentoo.org mailing list



  reply	other threads:[~2006-03-29  4:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28 13:19 [gentoo-kernel] [ANNOUNCE] genpatches-2.6.16-2 release Daniel Drake 
2006-03-28 13:26 ` John Mylchreest
2006-03-28 16:48   ` Daniel Drake
2006-03-28 17:09     ` Henrik Brix Andersen
2006-03-29  4:37       ` Kumba [this message]
2006-03-29  6:59         ` Henrik Brix Andersen
2006-03-29  9:44         ` John Mylchreest

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=442A0EFB.1050500@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=gentoo-kernel@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox