[gentoo-desktop] Re: How to mask KDE 4.6.2?

[Duncan]

Alex Schuster posted on Sun, 03 Apr 2011 20:35:30 +0200 as excerpted:

> Marián Kyral writes:
>
>> I'm using the EMERGE_DEFAULT_OPTS="--keep-going"
>> portage option to ignore missing files. This is enough for me.
>
> Not for me. I had tried the world update this night, but after a few
> packages (kde-env being the only KDE4-one) it failed to download oxygen-
> icons, and was unable to resume. Some of the packages that have updates
> pending are ffmpeg or glib, I don't understand why missing KDE4 stuff
> prevents their update.

Do you have FEATURES=parallel-fetch enabled?  Either that, or doing an 
emerge --upgrade --fetchonly --keep-going (with --newuse --deep --whatever 
as you normally do it) should help with that.

For ffmpeg, etc, it may be that they're inter-related to the kde 
dependencies in such a way that they don't want to update by themselves, 
however.

What I often do here when there's a pending kde update, even when it's 
available, is do an emerge --update --pretend (--newuse/deep...whatever) 
piped to grep -v kde.  That gives me a list of all the NON-KDE things to 
upgrade, (grep's -v reverses the grep so it lists anything WITHOUT the 
grepped term), and I'll then upgrade them first, manually.

The reasoning is that by breaking huge updates into smaller pieces, 
they're easier to handle.  This is particularly true for openrc, bash, 
glibc, etc updates, which I like doing by themselves, then testing, before 
I make any possible problems with such core components (I /am/ running 
~arch so they WILL happen from time to time!) more complex by compounding 
them several times over.  But a kde update is so huge by itself, that I 
prefer doing everything else first, not only the package updates 
themselves but also the etc-updates and non-kde revdep-rebuilds, before 
tackling kde, all by itself.

It works for me, altho sometimes if I've not upgraded for awhile, I end up 
typing in several packages at a time to upgrade, then several more 
(sometimes in a different konsole window, running the updates in parallel 
taking care not to duplicate dependency updates in more than one parallel 
session), until I get them all done.  That may be more bother than some 
people like, typing the individual packages in manually (either have --
oneshot in default-opts or always use it, I have scriptlets that use it by 
default), but at least here, I've found it easier to do that, than to 
troubleshoot new problems after the fact, when doing so has been made far 
more complex because of all the updates I did at the same time.  YMMV, but 
it works for me. =:^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman