From: Marcus Wanner <marcusw@cox.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Firefox 3.5 without changing entire system to ~arch?
Date: Mon, 02 Nov 2009 15:32:10 -0500 [thread overview]
Message-ID: <4AEF41CA.8060806@cox.net> (raw)
In-Reply-To: <5bdc1c8b0911021211w1dc38c73yefd867ebe37829a1@mail.gmail.com>
On 11/2/2009 3:11 PM, Mark Knecht wrote:
> On Mon, Nov 2, 2009 at 11:22 AM, Marcus Wanner <marcusw@cox.net> wrote:
> <SNIP>
>
>> Thank you, I added firefox and xulrunner to package.keywords and that did
>> the trick.
>>
>> Marcus
>>
>>
>>
>
> 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.
>
> 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.
>
> good luck,
> Mark
>
Thanks for the tip and the help, I'll make sure to keep that list short.
The only program I have this kind problem with is firefox, though, with
everything else I can get by with an older version. It's really becuase
Mozilla doesn't really support the older versions. Oh well, it will be
fixed eventually.
Marcus
next prev parent reply other threads:[~2009-11-02 20:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 17:16 [gentoo-user] Firefox 3.5 without changing entire system to ~arch? Marcus Wanner
2009-11-02 18:26 ` [gentoo-user] " Nikos Chantziaras
2009-11-02 6:43 ` Marcus Wanner
2009-11-02 18:39 ` [gentoo-user] " Alex Schuster
2009-11-02 18:40 ` Mike Edenfield
2009-11-02 19:22 ` Marcus Wanner
2009-11-02 20:11 ` Mark Knecht
2009-11-02 20:32 ` Marcus Wanner [this message]
2009-11-02 22:28 ` Alex Schuster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AEF41CA.8060806@cox.net \
--to=marcusw@cox.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox