On Wed, 29 Jan 2014 16:09:31 +0200, Thanasis <thana...@asyr.hopto.org>
wrote:
> on 01/28/2014 10:12 PM eroen wrote the following:
> > On Tue, 28 Jan 2014 21:29:21 +0200, Thanasis
> > <thana...@asyr.hopto.org> wrote:
> >> Is there a way to specify that I want to install (emerge) the
> >> latest 3.10.X series of sys-kernel/gentoo-sources as a slot, in
> >> parallel with the latest gentoo-sources?
> >>
> >> Currently, that would be version 3.10.28.
> >> I know I can specify it like so,
> >> emerge =sys-kernel/gentoo-sources-3.10.28
> >>
> >> but then it would not get "auto-updated" when a newer version of
> >> that series (for example 3.10.29) becomes available in portage.
> > 
> > Afaik there is no configuration-only way to do this, but you can
> > make it happen by adding your own virtual ebuilds in a local
> > overlay[1], say virtual/thanasis-sources, then adding that to world.
> > 
> > You can make one ebuild for each kernel-series you want, each in its
> > own slot, using the =cat/pkg-3.10* syntax for RDEPEND. Find
> > attached a (barely tested) suggestion for
> > virtual/thanasis-sources/thanasis-sources-3.10.ebuild . 
> 
> Thanks eroen, I tested it and it looks like it works.
> 
> One caveat,
> > =cat/pkg-3.10* also matches cat/pkg-3.107.1, 
> 
> I guess that kernel versions >= 3.100 are going to be in the tree, if
> ever, probably in about a decade from now :P
> 
> > which could become an
> > issue if you wanted, say, the 3.2 series.
> 
> Why would that be a problem?
> In the ebuild, you specified the value
> RDEPEND="=sys-kernel/gentoo-sources-${PV}*"

I think you got it, but then I confused you with a poorly chosen
example. The problem I referred to; if you try this exact method to
follow the 3.2.x kernels, you will switch to 3.20.0 when that comes
around. Similarly, it does not currently work with 3.1.x, and could
eventually (in a very long time, like you commented :P ) break for
other versions.

It would be nice to have a better way to accomplish this, perhaps
with some sort of world file variant supporting version ranges. That
could also be more intuitive and less prone to unintended consequences
(especially in the face of SLOTs) than package.mask-ing newer versions
to keep an old version of something around.

-- 
eroen

Attachment: signature.asc
Description: PGP signature

Reply via email to