public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Q on keywording java and xorg
Date: Thu, 6 Jul 2006 20:11:57 -0700	[thread overview]
Message-ID: <7573e9640607062011s8641f26ied3e2aff826c8713@mail.gmail.com> (raw)
In-Reply-To: <1152235327.2896.19.camel@localhost>

On 7/6/06, W.Kenworthy <billk@iinet.net.au> wrote:
> Is there a way to easily stop the system upgrading until the stable
> packages catch up? - without breakages?

Use version masks in your keywords file.  So rather than

x11-base/xorg-x11 ~x86

Use

<x11-base/xorg-x11-7.1

This will allow ~x86 versions of xorg 7.0, but wait until 7.1 goes
stable before upgrading to that.  You can use the specific version of
a ~x86 package that is available now if you like...but be careful if
you do this as some versions might disappear from portage without ever
going stable, causing portage to want to downgrade something back to
stable.

As far as going back to stable, it should be no more risky than going
~x86.  Just remove the keywords, and "emerge -DNv world" will give you
the stable versions of those packages.  The standard revdep-rebuild
and the like will still apply, just as with an "update".

One useful trick for seeing what versions you might want to backup to
is to export ACCEPT_KEYWORDS=-~x86 and use --pretend.  For example:

ACCEPT_KEYWORDS=-~x86 emerge -Dvp world

will show you every ~x86 package you have installed, and what the
stable version is.

-Richard
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-07-07  3:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07  1:22 [gentoo-user] Q on keywording java and xorg W.Kenworthy
2006-07-07  3:11 ` Richard Fish [this message]
2006-07-07  3:13   ` Richard Fish
2006-07-07 12:28   ` Benno Schulenberg
2006-07-07 17:12     ` Richard Fish
2006-07-07 20:18       ` Benno Schulenberg
2006-07-07 20:36         ` Richard Fish

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=7573e9640607062011s8641f26ied3e2aff826c8713@mail.gmail.com \
    --to=bigfish@asmallpond.org \
    --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