public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Holly Bostick <motub@planet.nl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Subversion 1.2
Date: Thu, 14 Jul 2005 22:58:21 +0200	[thread overview]
Message-ID: <42D6D1ED.8050409@planet.nl> (raw)
In-Reply-To: <42D6C170.6090402@shic.co.uk>

Steve [Gentoo] schreef:

> when I use ACCEPT_KEYWORDS in place of USE it now behaves just how I had
> previously expected it should have done.
> 
> # ACCEPT_KEYWORDS="~x86" emerge -uD subversion
> 
> This does what I'd originally intended to try...  (and doesn't force me
> to remember how to spell the  dependencies.) I assume there's no
> significant advantage I've missed in preferring to use the
> package.keywords file instead?

Advantage in using ACCEPT_KEYWORDS over /etc/portage/package.keywords?
Only in the case that you want to quickly test an unstable package, but
are not sure if you want to keep it.

The thing is.... Portage doesn't *remember* ACCEPT_KEYWORDS, beyond the
 original compile in which it is used. So if you use it, and keep the
package, as soon as you do an emerge -u world, Portage will try to
downgrade the package to the last stable version, which is the only one
that it knows to be allowed (because /etc/make.conf says "xarch", not
"~arch", and no exception for this particular package and its
dependencies has been made in /etc/portage/package.keywords).

This becomes especially frustrating if you do an emerge -uD world, and
it's not the main package, but one of the *dependencies* or deep
dependencies which forces a downgrade-- if the formerly unstable package
has been upgraded to stable, but depends on a package that has not yet
been upgraded, emerge -U(D) world can quickly become a hellish cycle of
the main package downgrading and then upgrading in the same or
sequential operations.... until you add the relevant packages to
/etc/portage/package.keywords and stop the madness.

However, if you find that the package is in fact too unstable for your
needs, the fact that it will be automatically downgraded at your next
emerge -u world is a nice safety net-- but you only need a safety net if
you're explicitly testing something and really don't know if it's going
to work out for you or not. If you know you want it, then add it to
package.keywords. If you're not sure, but don't have the time or energy
to explicitly test and make a final determination, then wait until it's
stable.

It's a beautiful system :-) .

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



  reply	other threads:[~2005-07-14 21:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-14 15:32 [gentoo-user] Subversion 1.2 Steve [Gentoo]
2005-07-14 17:02 ` Kurt Guenther
2005-07-14 17:26 ` Marco Matthies
2005-07-14 18:20   ` Steve [Gentoo]
2005-07-14 18:35     ` Petteri Räty
2005-07-14 19:48       ` Steve [Gentoo]
2005-07-14 20:58         ` Holly Bostick [this message]
2005-07-15 14:55           ` Steve [Gentoo]
2005-07-15 15:18             ` Zac Medico
2005-07-14 23:12     ` Marco Matthies

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=42D6D1ED.8050409@planet.nl \
    --to=motub@planet.nl \
    --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