From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] how do I keep package from being updated?
Date: Thu, 11 Jan 2007 09:21:06 -0600 [thread overview]
Message-ID: <200701110921.18366.bss03@volumehost.net> (raw)
In-Reply-To: <m3d55lfwi0.fsf@ccs.covici.com>
[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]
On Thursday 11 January 2007 08:50, John Covici <covici@ccs.covici.com>
wrote about '[gentoo-user] how do I keep package from being updated?':
> Hi. I just did emerge --pretend --update --deep world, but there is a
> package which I don't want to have emerge update automatically -- how
> do I accomplish this?
Add an appropriate atom to your /etc/portage/package.mask file. There's a
good section in the handbook about this, as well as it being documented in
the various man pages installed with portage, such as man portage, man
ebuild, and man 5 ebuild.
Very quickly:
If you have cate-gory/package-1.5.3 installed, and
cate-gory/package-1.6.0_rc2 is available but you don't want to upgrade,
add >=cate-gory/package-1.6* to your package.mask
(If it's a -rX upgrade, or and increase in the 3rd (or later) number in the
version, you probably want the upgrade. Really. The former is an ebuild
fix that won't change the upstream version you get (so, you will almost
never encounter upgrade issues); the later is (for most packages) a
security or bugfix release that should maintain compatibility with
previous versions (so, you will rarely encounter upgrade issues).)
--
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-01-11 15:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 14:50 [gentoo-user] how do I keep package from being updated? John Covici
2007-01-11 15:10 ` Hans-Werner Hilse
2007-01-11 16:32 ` John covici
2007-01-11 16:38 ` John covici
2007-01-11 16:56 ` Hans-Werner Hilse
2007-01-11 17:36 ` Bo Ørsted Andresen
2007-01-11 17:56 ` John covici
2007-01-11 18:09 ` Bo Ørsted Andresen
2007-01-11 18:09 ` Ryan Sims
2007-01-11 16:47 ` Neil Bothwick
2007-01-11 17:28 ` Bo Ørsted Andresen
2007-01-11 20:32 ` Neil Bothwick
2007-01-11 20:43 ` Bo Ørsted Andresen
2007-01-11 21:43 ` John covici
2007-01-11 21:51 ` kashani
2007-01-11 22:20 ` Bo Ørsted Andresen
2007-01-11 22:41 ` Neil Bothwick
2007-01-11 15:21 ` Boyd Stephen Smith Jr. [this message]
2007-01-11 17:30 ` Bo Ørsted Andresen
2007-01-11 17:48 ` Boyd Stephen Smith Jr.
2007-01-11 18:11 ` kashani
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=200701110921.18366.bss03@volumehost.net \
--to=bss03@volumehost.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