[gentoo-user] How to control SLOT?

[gentoo-user] How to control SLOT?

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 970 bytes --]

After all these years I still can't find my way around SLOT management needed 
for enlightenment.

I want to emerge the latest available in the tree, which right now happens to 
be (~) 0.18.7.  So I added this in my keywords:

>=x11-wm/enlightenment-0.18.7:0.17 ~amd64

However, if I try:
==========================================================================
# emerge -1aDv enlightenment

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  NS    ] x11-wm/enlightenment-1.0.11:0 [0.18.7:0.17/0.18.7] USE="dbus 
nls pango -doc -pulseaudio -xcomposite -xinerama -xrandr" 2,229 kB

Total: 1 package (1 in new slot), Size of downloads: 2,229 kB
==========================================================================

It wants to bring in e16, of SLOT 0, instead of 0.18.7 SLOT 0.17.  Can you 
please explain to me how this is meant to work and what the correct syntax is?

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-user] How to control SLOT?

[Alan McKinnon]

On 16/05/2014 14:38, Mick wrote:
> After all these years I still can't find my way around SLOT management needed 
> for enlightenment.
> 
> I want to emerge the latest available in the tree, which right now happens to 
> be (~) 0.18.7.  So I added this in my keywords:
> 
>> =x11-wm/enlightenment-0.18.7:0.17 ~amd64

Either drop the "=" or drop the SLOT ":0.17"

= always means a specific version is to be specified and a SLOT is not a
version

> 
> However, if I try:
> ==========================================================================
> # emerge -1aDv enlightenment
> 
> These are the packages that would be merged, in order:
> 
> Calculating dependencies... done!
> [ebuild  NS    ] x11-wm/enlightenment-1.0.11:0 [0.18.7:0.17/0.18.7] USE="dbus 
> nls pango -doc -pulseaudio -xcomposite -xinerama -xrandr" 2,229 kB
> 
> Total: 1 package (1 in new slot), Size of downloads: 2,229 kB
> ==========================================================================
> 
> It wants to bring in e16, of SLOT 0, instead of 0.18.7 SLOT 0.17.  Can you 
> please explain to me how this is meant to work and what the correct syntax is?


Your keyword entry applies to nothing in the tree, so you get the
expected result, the latest stable version of e



-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] How to control SLOT?

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 830 bytes --]

On Friday 16 May 2014 13:44:37 Alan McKinnon wrote:
> On 16/05/2014 14:38, Mick wrote:
> > After all these years I still can't find my way around SLOT management
> > needed for enlightenment.
> > 
> > I want to emerge the latest available in the tree, which right now
> > happens to be (~) 0.18.7.  So I added this in my keywords:
> >  > =x11-wm/enlightenment-0.18.7:0.17 ~amd64
> 
> Either drop the "=" or drop the SLOT ":0.17"
> 
> = always means a specific version is to be specified and a SLOT is not a
> version

OK, dropping "=" still wants to install e16.

Dropping ">" still wants to install e16.

Dropping the SLOT ":0.17" still wants to install e16.


There must be some way of bringing in any >=0.18.7:0.17, but not 'x11-
wm/enlightenment-1.0.11:0'

What else could I try?
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-user] How to control SLOT?

[Alan McKinnon]

On 16/05/2014 18:03, Mick wrote:
> On Friday 16 May 2014 13:44:37 Alan McKinnon wrote:
>> On 16/05/2014 14:38, Mick wrote:
>>> After all these years I still can't find my way around SLOT management
>>> needed for enlightenment.
>>>
>>> I want to emerge the latest available in the tree, which right now
>>> happens to be (~) 0.18.7.  So I added this in my keywords:
>>>  > =x11-wm/enlightenment-0.18.7:0.17 ~amd64
>>
>> Either drop the "=" or drop the SLOT ":0.17"
>>
>> = always means a specific version is to be specified and a SLOT is not a
>> version
> 
> OK, dropping "=" still wants to install e16.
> 
> Dropping ">" still wants to install e16.
> 
> Dropping the SLOT ":0.17" still wants to install e16.
> 
> 
> There must be some way of bringing in any >=0.18.7:0.17, but not 'x11-
> wm/enlightenment-1.0.11:0'
> 
> What else could I try?
> 

There's nothing special about E anymore, it isn't package.masked, it's
simply keyworded ~amd64 ~arm ~x86

Are you running amd64 or ~amd64?
Do you have some local package.mask blocking e17?

Here's my setting that work for me:

$ grep ACCEPT_KEYWORDS /etc/portage/make.conf
ACCEPT_KEYWORDS="~amd64"

$ grep enlightenment /var/lib/portage/world
x11-wm/enlightenment

$ grep -ir enlightenment /etc/portage
/etc/portage/package.mask/package.mask:x11-wm/enlightenment:0



So you *should" be able to just keyword e17 and have it work:

echo "x11-wm/enlightenment" >> /etc/portage/package.accept_keywords

-- 
Alan McKinnon
alan.mckinnon@gmail.com

[gentoo-user] Re: How to control SLOT?

[Jörg Schaible]

Mick wrote:

> On Friday 16 May 2014 13:44:37 Alan McKinnon wrote:
>> On 16/05/2014 14:38, Mick wrote:
>> > After all these years I still can't find my way around SLOT management
>> > needed for enlightenment.
>> > 
>> > I want to emerge the latest available in the tree, which right now
>> > happens to be (~) 0.18.7.  So I added this in my keywords:
>> >  > =x11-wm/enlightenment-0.18.7:0.17 ~amd64
>> 
>> Either drop the "=" or drop the SLOT ":0.17"
>> 
>> = always means a specific version is to be specified and a SLOT is not a
>> version
> 
> OK, dropping "=" still wants to install e16.
> 
> Dropping ">" still wants to install e16.
> 
> Dropping the SLOT ":0.17" still wants to install e16.
> 
> 
> There must be some way of bringing in any >=0.18.7:0.17, but not 'x11-
> wm/enlightenment-1.0.11:0'
> 
> What else could I try?

x11-wm/enlightenment:0.17 ~amd64

- Jörg

Re: [gentoo-user] How to control SLOT?

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 880 bytes --]

On Friday 16 May 2014 17:30:06 Alan McKinnon wrote:

> There's nothing special about E anymore, it isn't package.masked, it's
> simply keyworded ~amd64 ~arm ~x86
> 
> Are you running amd64 or ~amd64?
> Do you have some local package.mask blocking e17?

I'm running amd64 with the odd exception (like enlightenment) and I have no 
enlightenment related masks set up.

> Here's my setting that work for me:
> 
> $ grep ACCEPT_KEYWORDS /etc/portage/make.conf
> ACCEPT_KEYWORDS="~amd64"
> 
> $ grep enlightenment /var/lib/portage/world
> x11-wm/enlightenment
> 
> $ grep -ir enlightenment /etc/portage
> /etc/portage/package.mask/package.mask:x11-wm/enlightenment:0

Ahh!  You have masked SLOT :0 to stop e16 being pulled in.  I thought that 
this would be achievable somehow, merely by keywording SLOT :0.17, but without 
masking e16.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-user] Re: How to control SLOT?

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 709 bytes --]

On Friday 16 May 2014 18:09:08 Jörg Schaible wrote:
> Mick wrote:

> > What else could I try?
> 
> x11-wm/enlightenment:0.17 ~amd64

Thanks Jörg, this (partly) worked and put me on the right path.  So, now I 
have in /etc/portage/package.keywords/enlightenment:

  x11-wm/enlightenment:0.17 ~amd64


and in /etc/portage/sets/enlightenment:

  x11-wm/enlightenment:0.17


Portage no longer tries to pull in e16 when I emerge set '@enlightenment' 
because the latter is only asking for SLOT :0.17.  Of course, if I try 'emerge 
-1aDv enlightenment', then all bets are off without explicitly masking e16 off 
as Alan has done.

Thank you both for your help!  :-)

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-user] How to control SLOT?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 553 bytes --]

On Fri, 16 May 2014 20:25:21 +0100, Mick wrote:

> > $ grep -ir enlightenment /etc/portage
> > /etc/portage/package.mask/package.mask:x11-wm/enlightenment:0  
> 
> Ahh!  You have masked SLOT :0 to stop e16 being pulled in.  I thought
> that this would be achievable somehow, merely by keywording SLOT :0.17,
> but without masking e16.

You are running "emerge enlightenment" which defaults to slot 0. you
could mask slot 0 like Alan has or you could emerge enlightenment:0.17


-- 
Neil Bothwick

How do I set my laser printer to stun?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: How to control SLOT?

[Alan McKinnon]

On 16/05/2014 21:34, Mick wrote:
> On Friday 16 May 2014 18:09:08 Jörg Schaible wrote:
>> Mick wrote:
> 
>>> What else could I try?
>>
>> x11-wm/enlightenment:0.17 ~amd64
> 
> Thanks Jörg, this (partly) worked and put me on the right path.  So, now I 
> have in /etc/portage/package.keywords/enlightenment:
> 
>   x11-wm/enlightenment:0.17 ~amd64
> 
> 
> and in /etc/portage/sets/enlightenment:
> 
>   x11-wm/enlightenment:0.17
> 
> 
> Portage no longer tries to pull in e16 when I emerge set '@enlightenment' 
> because the latter is only asking for SLOT :0.17.  Of course, if I try 'emerge 
> -1aDv enlightenment', then all bets are off without explicitly masking e16 off 
> as Alan has done.


I can remove that masking from here now, it dates back years to when e17
was in an overlay with some peculiar masking applied. Portage too many
times would miss an update and want to install e16 so the easiest was to
just mask it locally.

I don't really need that anymore, so thanks for getting me to look there :-)

-- 
Alan McKinnon
alan.mckinnon@gmail.com