1 |
On 16/05/2014 14:38, Mick wrote: |
2 |
> After all these years I still can't find my way around SLOT management needed |
3 |
> for enlightenment. |
4 |
> |
5 |
> I want to emerge the latest available in the tree, which right now happens to |
6 |
> be (~) 0.18.7. So I added this in my keywords: |
7 |
> |
8 |
>> =x11-wm/enlightenment-0.18.7:0.17 ~amd64 |
9 |
|
10 |
Either drop the "=" or drop the SLOT ":0.17" |
11 |
|
12 |
= always means a specific version is to be specified and a SLOT is not a |
13 |
version |
14 |
|
15 |
> |
16 |
> However, if I try: |
17 |
> ========================================================================== |
18 |
> # emerge -1aDv enlightenment |
19 |
> |
20 |
> These are the packages that would be merged, in order: |
21 |
> |
22 |
> Calculating dependencies... done! |
23 |
> [ebuild NS ] x11-wm/enlightenment-1.0.11:0 [0.18.7:0.17/0.18.7] USE="dbus |
24 |
> nls pango -doc -pulseaudio -xcomposite -xinerama -xrandr" 2,229 kB |
25 |
> |
26 |
> Total: 1 package (1 in new slot), Size of downloads: 2,229 kB |
27 |
> ========================================================================== |
28 |
> |
29 |
> It wants to bring in e16, of SLOT 0, instead of 0.18.7 SLOT 0.17. Can you |
30 |
> please explain to me how this is meant to work and what the correct syntax is? |
31 |
|
32 |
|
33 |
Your keyword entry applies to nothing in the tree, so you get the |
34 |
expected result, the latest stable version of e |
35 |
|
36 |
|
37 |
|
38 |
-- |
39 |
Alan McKinnon |
40 |
alan.mckinnon@×××××.com |