From: Eric Thibeault Jolin <irise-lenoir@sympatico.ca>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] package.mask
Date: Fri, 07 Jun 2002 15:27:42 -0400 [thread overview]
Message-ID: <3D01092E.5020003@sympatico.ca> (raw)
Portage works like a charm, but it is a chore to use package.masked
stuff and update often.
I want a /etc/package.mask file that doesn't get modified by portage and
overrides /usr/portage/profile/package.mask. I also want the ability to
write something like "! >=gnome-base/gnome-2.0.0_beta5" to force
unmasking a package. But user masking will be nice too, like to force
not installing jdk 1.4 on "emerge--update world" or to "remove nautilus
from gnome-base", at least in effect. When I said portage shouldn't
tamper with it, a possible exception might be when a package forced
unmasked in /etc is permanently removed from
/usr/portage/profile/package.mask, it might be good to remove it from
/etc/package.mask (respecting config protection, of course).
On the other point of view, a /etc/package.protect file might be useful
to manually protect a package or version of package from being removed
by "emerge clean".
As I said, it already works wonders, but these small changes and it will
be perfect! Okay, maybe not... almost perfect.
next reply other threads:[~2002-06-07 19:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-07 19:27 Eric Thibeault Jolin [this message]
2002-06-07 19:28 ` [gentoo-dev] package.mask Tom Syroid
-- strict thread matches above, loose matches on Subject: below --
2001-12-10 22:29 Zach Forrest
2001-12-10 22:56 ` Geert Bevin
2001-12-11 0:22 ` Zach Forrest
2001-04-13 15:19 Daniel Robbins
2001-04-14 9:24 ` Achim Gottinger
2001-04-14 10:21 ` Daniel Robbins
2001-04-14 11:44 ` Achim Gottinger
2001-04-14 12:19 ` Daniel Robbins
2001-04-14 12:40 ` Achim Gottinger
2001-04-14 13:35 ` Daniel Robbins
2001-04-14 14:28 ` Achim Gottinger
2001-04-14 15:28 ` Daniel Robbins
2001-04-15 3:27 ` Achim Gottinger
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=3D01092E.5020003@sympatico.ca \
--to=irise-lenoir@sympatico.ca \
--cc=gentoo-dev@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