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 :)  

Its more like the testing. ~arch is when a developer deems his package ready
for inclusion. 

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

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, people
which are using pre-vanilla-sources will be stuck at the latest _pre (or
_testing).

And when they emerge the vanilla-sources, they'll miss the next _pre cycle.
 
Personally, I would go for package.mask

Wkr,
	Sven Vermeulen

-- 
    Save some animals, eat a vegetarian.