Mark Knecht writes:
> On Mon, Nov 2, 2009 at 11:22 AM, Marcus Wanner <[email protected]> wrote:
> <SNIP>
>
> > Thank you, I added firefox and xulrunner to package.keywords and that
> > did the trick.
> You might want to periodically run eix-test-obsolete -d to see if the
> two packages get marked stable before some other new ~arch version
> comes out. If that happens, and it often does in my experience, then
> you can remove the two packages from portage.keywords and you're back
> to running stable.
When I need to unmask something in package.keywords, I prefer to put the
package along with its version number in it. I leave out the trailing -rN,
and start with ~ instead of =, which means that minor revision updates
(increasing the -rN) which often are security fixes are also matched.
Talking about firefox, I just added these two lines before I replied to this
thread some hours ago:
~www-client/mozilla-firefox-3.5.3
~net-libs/xulrunner-1.9.1.4
When a newer ~arch xulrunner enters the portage tree, it will not be
upgraded.
There are also some packages which I like to be always the new version, so I
leave out the version number. firefox could be such an application. But for
everything I have to unmask additionally, I add the version numbers.
I use eix-test-obsolete once in a while in order to clean this of redundant
entries.
> In general I tend to have 4 or 5 packages in package.keywords at any
> given time. I don't have too much trouble. Watch out if the list
> starts getting large though as things get messy and you'll find
> yourself doing more updates than maybe you want to be doing.
Oh, my package.keywords is quite large, with about 50 entries. Oh, and the
300 entries for KDE 4.3.
Wonko
