1 |
On 28/01/2014 22:04, Thanasis wrote: |
2 |
> on 01/28/2014 09:36 PM Andrew Tselischev wrote the following: |
3 |
>> On Tue, Jan 28, 2014 at 09:29:21PM +0200, Thanasis 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 |
>> |
16 |
>> You could mask "newer" versions in package.mask like so: |
17 |
>> |
18 |
>>> =sys-kernel/gentoo-sources-3.10.29* |
19 |
>> |
20 |
>> |
21 |
> |
22 |
> Maybe I was not so clear, but my intent is *NOT* to mask any newer |
23 |
> versions, but have the sys-kernel/gentoo-sources-3.10.X get updated as a |
24 |
> slot, in parallel to latest sys-kernel/gentoo-sources, when I do a world |
25 |
> update like so: |
26 |
> emerge -DNu world |
27 |
|
28 |
|
29 |
that won't work as each kernel ebuild is in it's own unique slot |
30 |
consisting of one and only one kernel version. I doubt the kernel team |
31 |
are going to change that. |
32 |
|
33 |
What you are asking is fundamentally not possible as slots are used in a |
34 |
very incompatible way with your idea. |
35 |
|
36 |
You will have to find and accept a workaround, such as masks. |
37 |
|
38 |
But it's not really that big of a deal. Kernels ebuilds are sources, |
39 |
they build no binaries. Having a version installed doesn't mean it runs, |
40 |
it means you have the sources. All it consumes is disk space as they |
41 |
don;tget updated |
42 |
|
43 |
-- |
44 |
Alan McKinnon |
45 |
alan.mckinnon@×××××.com |