public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Rickard <frogger@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Where to put prerelease vanilla kernels?
Date: Wed, 23 Jul 2003 12:16:03 -0400	[thread overview]
Message-ID: <20030723121603.11ab807e.frogger@gentoo.org> (raw)

Portage currently does not contain any vanilla prerelease kernels (i.e.
2.4.22_pre7).  Bug 25107 is a request for this, and it seems reasonable
to have these kernels in portage, since we have pretty much every other
kernel branch you could think of in there :)

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 :)  We could also package.mask them here, this
might emphasize the fact that they are not supported.  However, _pre
kernels are generally quite stable, probably more so than many of the
other kernel branches we provide in portage.

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.

Any comments or suggestions on this?  I'm hoping for some kind of
consensus on where these should be put.

Thanks.

--
Matt Rickard
frogger@gentoo.org



--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-07-23 16:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23 16:16 Matt Rickard [this message]
2003-07-23  7:10 ` [gentoo-dev] Where to put prerelease vanilla kernels? Alvaro Figueroa Cabezas
2003-07-23 19:16   ` Chris Gianelloni
2003-07-23  7:46     ` Alvaro Figueroa Cabezas
2003-07-23 20:03       ` donnie berkholz
2003-07-23  8:28         ` Alvaro Figueroa Cabezas
2003-07-23 20:51           ` Peter Johanson
2003-07-23 22:35           ` Chris Gianelloni
2003-07-23 19:21     ` donnie berkholz
2003-07-23 17:45 ` Jay Pfeifer
2003-07-23 19:39   ` Matt Rickard
2003-07-23 18:06 ` Dhruba Bandopadhyay
2003-07-23 18:24   ` Jay Pfeifer
2003-07-24  8:28 ` Sven Vermeulen
2003-07-24  9:07   ` Georgi Georgiev
2003-07-24 13:07     ` Matt Rickard
2003-07-24 13:38       ` Paul de Vrieze
2003-07-24 14:13         ` Terje Kvernes
2003-07-24 12:56   ` Matt Rickard
2003-07-24 13:49     ` Thomas de Grenier de Latour
2003-07-24 13:54       ` Thomas de Grenier de Latour
2003-08-25 17:43   ` Alvaro Figueroa

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=20030723121603.11ab807e.frogger@gentoo.org \
    --to=frogger@gentoo.org \
    --cc=gentoo-dev@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