[gentoo-user] Syntax for masking kde:4?

Am Sonntag 11 Oktober 2009 13:30:06 schrieb Peter Humphrey:

> What is the syntax for a single entry in package.mask to exclude the whole
> of kde:4?

When using paludis, that would be

=kde-base/*:4.3

or more general:

=<category>/*:<slot>

Don't know wether this works the same with portage, though.

HTH...

Dirk

On 10/11/2009 02:30 PM, Peter Humphrey wrote:
> Hello list,
>
> In the last few days some parts of KDE v4 seem to have been moved into the
> stable tree, but on some of my boxes I want to exclude kde:4 (but not qt:4).
>
> What is the syntax for a single entry in package.mask to exclude the whole of
> kde:4? I did start masking each package separately, but that's far too much
> work - I'd finish up with an entry for every kde package that has a version
> 4. Also, "kde:4", which seems like the right thing to specify, is an invalid
> package atom according to eix.
>
> I can't see anything relevant in man pages or the gentoo kde configuration
> guide. Google hasn't helped me either.

Portage unfortunately doesn't allow wildcards in the package name of
atoms. But you can install KDE4 on one machine and then use:

qlist -ISLC kde-base/*:4.3

to generate a list to put in package.mask in the machines you don't want
KDE4. On my machine, the above command results in the following (it
should at least cut down on the rest of the packages you need to mask):

kde-base/ark:4.3
kde-base/dolphin:4.3
kde-base/drkonqi:4.3
kde-base/gwenview:4.3
kde-base/kamera:4.3
kde-base/kappfinder:4.3
kde-base/kapptemplate:4.3
kde-base/kate:4.3
kde-base/kcalc:4.3
kde-base/kcheckpass:4.3
kde-base/kcminit:4.3
kde-base/kcmshell:4.3
kde-base/kcolorchooser:4.3
kde-base/kcontrol:4.3
kde-base/kde-env:4.3
kde-base/kdeartwork-colorschemes:4.3
kde-base/kdeartwork-desktopthemes:4.3
kde-base/kdeartwork-emoticons:4.3
kde-base/kdeartwork-iconthemes:4.3
kde-base/kdeartwork-kscreensaver:4.3
kde-base/kdeartwork-meta:4.3
kde-base/kdeartwork-sounds:4.3
kde-base/kdeartwork-styles:4.3
kde-base/kdeartwork-wallpapers:4.3
kde-base/kdeartwork-weatherwallpapers:4.3
kde-base/kdebase-cursors:4.3
kde-base/kdebase-data:4.3
kde-base/kdebase-desktoptheme:4.3
kde-base/kdebase-kioslaves:4.3
kde-base/kdebase-menu:4.3
kde-base/kdebase-menu-icons:4.3
kde-base/kdebase-meta:4.3
kde-base/kdebase-startkde:4.3
kde-base/kdebase-wallpapers:4.3
kde-base/kdebugdialog:4.3
kde-base/kdegraphics-meta:4.3
kde-base/kdegraphics-strigi-analyzer:4.3
kde-base/kdelibs:4.3
kde-base/kdepasswd:4.3
kde-base/kdepimlibs:4.3
kde-base/kdeplasma-addons:4.3
kde-base/kdesu:4.3
kde-base/kdialog:4.3
kde-base/kdm:4.3
kde-base/kdnssd:4.3
kde-base/keditbookmarks:4.3
kde-base/keditfiletype:4.3
kde-base/kephal:4.3
kde-base/kfile:4.3
kde-base/kfind:4.3
kde-base/kfmclient:4.3
kde-base/kgamma:4.3
kde-base/kget:4.3
kde-base/kglobalaccel:4.3
kde-base/khelpcenter:4.3
kde-base/khotkeys:4.3
kde-base/kiconfinder:4.3
kde-base/kinfocenter:4.3
kde-base/kioclient:4.3
kde-base/klipper:4.3
kde-base/kmenuedit:4.3
kde-base/kmimetypefinder:4.3
kde-base/knetattach:4.3
kde-base/knewstuff:4.3
kde-base/knotify:4.3
kde-base/kolourpaint:4.3
kde-base/konqueror:4.3
kde-base/konsole:4.3
kde-base/kpasswdserver:4.3
kde-base/kquitapp:4.3
kde-base/krdc:4.3
kde-base/kreadconfig:4.3
kde-base/krosspython:4.3
kde-base/kruler:4.3
kde-base/krunner:4.3
kde-base/ksaneplugin:4.3
kde-base/kscreensaver:4.3
kde-base/ksmserver:4.3
kde-base/ksnapshot:4.3
kde-base/ksplash:4.3
kde-base/kstart:4.3
kde-base/kstartupconfig:4.3
kde-base/kstyles:4.3
kde-base/ksysguard:4.3
kde-base/ksystraycmd:4.3
kde-base/ktimezoned:4.3
kde-base/ktraderclient:4.3
kde-base/kuiserver:4.3
kde-base/kurifilter-plugins:4.3
kde-base/kwalletd:4.3
kde-base/kwin:4.3
kde-base/kwrite:4.3
kde-base/kwrited:4.3
kde-base/libkcddb:4.3
kde-base/libkdcraw:4.3
kde-base/libkexiv2:4.3
kde-base/libkipi:4.3
kde-base/libknotificationitem:4.3
kde-base/libkonq:4.3
kde-base/libksane:4.3
kde-base/libkworkspace:4.3
kde-base/libplasmaclock:4.3
kde-base/libtaskmanager:4.3
kde-base/nsplugins:4.3
kde-base/okular:4.3
kde-base/oxygen-icons:4.3
kde-base/phonon-kde:4.3
kde-base/plasma-apps:4.3
kde-base/plasma-runtime:4.3
kde-base/plasma-workspace:4.3
kde-base/powerdevil:4.3
kde-base/renamedlg-plugins:4.3
kde-base/solid:4.3
kde-base/solid-hardware:4.3
kde-base/solidautoeject:4.3
kde-base/soliduiserver:4.3
kde-base/svgpart:4.3
kde-base/systemsettings:4.3
kde-base/thumbnailers:4.3

On Sunday 11 October 2009 20:16:24 Nikos Chantziaras wrote:

> Portage unfortunately doesn't allow wildcards in the package name of
> atoms. But you can install KDE4 on one machine and then use:
>
> qlist -ISLC kde-base/*:4.3
>
> to generate a list to put in package.mask in the machines you don't want
> KDE4. On my machine, the above command results in the following (it
> should at least cut down on the rest of the packages you need to mask):

Excellent idea! I'll get started straight away - thanks Nikos.

A third possibility, besides the two I mentioned just now: a good dose of
lateral thinking.

--
Rgds
Peter

PS. Thanks also to Jonathan C who's saved me even that little trouble.

On Sunday 11 October 2009 22:30:29 Alan McKinnon wrote:

> Have you considered simply not installing them at all? If you don't want
> apache, cups, syslog-ng and bind you don't take any special steps, you
> simply don't emerge them.

No, but those are single packages, more or less. KDE is hundreds of packages -
not the same scale at all.

> Unless of course you do want kde:3.5 (I don't recall if you mentioned that
> or not).

Yes, where a GUI is installed it's kde:3.5, and I want to keep it, except on a
test box where it can be kept safely confined.

> OT: I really like kde:4 myself, but it's such a different product to
> kde:3.5 that I honestly feel it's official name should have been kde4. If
> the kde devs had done that, your issue would simply never have happened.
> This versioning is causing problems for many people, you are not the only
> one wanting to avoid kde:4

Oh woe! I've just run a sync and found another 25 of them. The other day I put
13 entries into package.mask and that held the fort for the time; now I have
another battle to fight. There will be more, too.

What I need is an automask to complement autounmask, or perhaps a kde4 USE
flag.

--
Rgds
Peter

Peter Humphrey wrote:
> On Sunday 11 October 2009 22:30:29 Alan McKinnon wrote:
>
>
>> Have you considered simply not installing them at all? If you don't want
>> apache, cups, syslog-ng and bind you don't take any special steps, you
>> simply don't emerge them.
>>
>
> No, but those are single packages, more or less. KDE is hundreds of packages -
> not the same scale at all.
>
>
>> Unless of course you do want kde:3.5 (I don't recall if you mentioned that
>> or not).
>>
>
> Yes, where a GUI is installed it's kde:3.5, and I want to keep it, except on a
> test box where it can be kept safely confined.
>
>
>> OT: I really like kde:4 myself, but it's such a different product to
>> kde:3.5 that I honestly feel it's official name should have been kde4. If
>> the kde devs had done that, your issue would simply never have happened.
>> This versioning is causing problems for many people, you are not the only
>> one wanting to avoid kde:4
>>
>
> Oh woe! I've just run a sync and found another 25 of them. The other day I put
> 13 entries into package.mask and that held the fort for the time; now I have
> another battle to fight. There will be more, too.
>
> What I need is an automask to complement autounmask, or perhaps a kde4 USE
> flag.
>
>

I would do as someone else suggested, run autounmask for kde 4 and move
the list package.unmask to package.mask. You would likely have to add
to that over time but it is at least a start. Keep in mind, once KDE 4
is stable, you can't use autounmask to do this since it is already
unmasked.

According to -dev, KDE 4 is going stable pretty soon.
http://bugs.gentoo.org/show_bug.cgi?id=287697 It's already in the works.

Dale

On Monday 12 October 2009 11:30:22 Peter Humphrey wrote:
> > OT: I really like kde:4 myself, but it's such a different product to
> > kde:3.5 that I honestly feel it's official name should have been kde4. If
> > the kde devs had done that, your issue would simply never have happened.
> > This versioning is causing problems for many people, you are not the only
> > one wanting to avoid kde:4
>
> Oh woe! I've just run a sync and found another 25 of them. The other day I
> put 13 entries into package.mask and that held the fort for the time; now
> I have another battle to fight. There will be more, too.

Yes, there will be more. And it's not likely to stop.

It really is a pity that two different products have the same name with
different slots. Causes no end of trouble, as you are seeing.

But it's too late to change it now

> What I need is an automask to complement autounmask, or perhaps a kde4 USE
> flag.

autounmask outputs a file, right? Move it from the package.unmask to the
package.mask area - the format is the same for both.

A USE flag won't help you here. USE s to enable/disable *features* of certain
packages, not enable/disable entire packages or prevent them from being
installed.

--
alan dot mckinnon at gmail dot com

On Wednesday 14 October 2009 13:38:53 Neil Bothwick wrote:

> grep ^kde-base /var/lib/portage/world | sed s/$/:4/
> >/etc/portage/package.mask/kde4

That's neat. Thanks - though it misses anything pulled in by world entries.

Meanwhile I've captured the file that Jonathan mentioned - and I've already
had to augment it to mask the latest versions of kdiff3 and kmplayer, which
want to exclude kde:3 libraries.

--
Rgds
Peter