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