From: "John J. Foster" <Gentoo-User@festus.150ml.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] package version notification (~/+)?
Date: Mon, 3 Jul 2006 22:34:17 -0400 [thread overview]
Message-ID: <20060704023417.GC8426@garbanzo> (raw)
In-Reply-To: <yu9wtauazny.fsf@nyu.edu>
[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]
On Mon, Jul 03, 2006 at 10:09:53PM -0400, Allan Gottlieb wrote:
> At Mon, 03 Jul 2006 21:06:07 -0400 "John J. Foster" <Gentoo-User@festus.150ml.com> wrote:
> >
> > Neil - I _think_ this is what I have not been able to understand for
> > over a year now. I run an almost entirely stable system, and want to
> > keep it that way. But occassionally there is something I want that is
> > currently ~x86, for instance amarok. So what you're saying is that if I
> >
> > #echo =media-sound/amarok-1.4.0a-r1 >> /etc/portage/package.keywords
> >
> > I will not get the next testing version of amarok, but will get the next
> > stable?
>
> Yes. The line you are adding to package.keywords says that for *the
> specific version listed* (since you begin with "=") you will emerge
> it, if it is keyworded (or stable). For any other version, in
> particular for the next version issued from upstream, the line you
> added says nothing. Hence, since you are running a stable system,
> only stable versions (except for 1.4.0a-r1) are eligible for emerging.
>
Excellent. Thanks Neil and Allan. You know, I just went back and re-read
the man page for portage, and it made perfect sense. I'd read that
fucking page probably 10 times before and didn't get it.
Thanks again,
festus
--
It is not unusual for those at the wrong end of the club to have a
clearer picture of reality than those who wield it.
Noam Chomsky
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-07-04 2:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 18:17 [gentoo-user] package version notification (~/+)? Jarry
2006-07-03 19:07 ` Neil Bothwick
2006-07-03 21:12 ` Etaoin Shrdlu
2006-07-04 1:06 ` John J. Foster
2006-07-04 2:09 ` Allan Gottlieb
2006-07-04 2:34 ` John J. Foster [this message]
2006-07-04 3:15 ` Allan Gottlieb
2006-07-04 3:43 ` Ryan Tandy
2006-07-04 6:50 ` Roy Wright
2006-07-04 12:21 ` Allan Gottlieb
2006-07-04 14:09 ` Bo Ørsted Andresen
2006-07-04 14:39 ` Allan Gottlieb
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=20060704023417.GC8426@garbanzo \
--to=gentoo-user@festus.150ml.com \
--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