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: Re: [gentoo-dev] Where to put prerelease vanilla kernels?
Date: Thu, 24 Jul 2003 09:07:06 -0400	[thread overview]
Message-ID: <20030724090706.37242e13.frogger@gentoo.org> (raw)
In-Reply-To: <20030724090711.GH30147%chutz@gg3.net>

> 
> I fully support the opinions stated above, and I simply cannot
> comprehend what the big deal with ~arch masking vanilla-sources is.
> Even *considering* the option of a separate package is ridiculous. As
> long as developers are careful enough to not remove the ~arch mask
> from any _pre kernel, I am perfectly fine, and I believe there
> wouldn't be anyone who isn't fine. What are we trying to do-- make
> sure people who insist on running the *unstable* profile actually
> don't get the "unstable" sources. 

Well the fact is that an unstable kernel can be a whole lot more
problematic than an unstable userland package.  With userland, if it
crashes, oh well, you can start it up again.  With an unstable kernel
you run the risk of hard locks and corrupted filesystems.

I know that I've used vanilla-sources on some systems where I'm using
the ~arch profile, because I KNOW it will work correctly.  Sometimes I
don't want to mess around with experimental kernel patches.

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? 

The point is that vanilla-sources gets you stable release kernels all
the time.

>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. 

Well beta kernels already have their own category as
development-sources.  It is my understanding that this _pre category
will also contain _rc kernels.

>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.

I hope you filed a bug report :)  I don't use gentoo-sources myself so I
can't comment anymore than that.

> 
> Sorry for the tone, but I feel frustrated.

No problem, you raise some issues that definitely do need to be
addressed.

--
Matt Rickard
frogger@gentoo.org


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-07-24 13:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23 16:16 [gentoo-dev] Where to put prerelease vanilla kernels? Matt Rickard
2003-07-23  7:10 ` 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 [this message]
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=20030724090706.37242e13.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