From: Helmut Jarausch <jarausch@igpm.rwth-aachen.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Which Comes First, the Unmask or the Mask?
Date: Wed, 20 Oct 2010 16:28:12 +0200 [thread overview]
Message-ID: <1287584892.6107.0@numa-i> (raw)
In-Reply-To: <4CBE4EBC.9070203@gmail.com>
On 10/20/10 04:06:52, Andy Wilkinson wrote:
> I believe I know the answer to the question... the real question is,
> how can I work around it? ;)
>
> I am running the development branch of www-client/chromium (currently
> 8.0.552.0). As a result, I like the latest builds to always be
> unmasked
> when they are available. However, once in a while there is a bad
> apple
> in the bunch and I'd like to mask that atom specifically. 8.0.552.0
> is
> one of those that I would like masked.
>
> What I'd like to do is:
>
> /etc/portage/package.unmask:
> www-client/chromium
>
> /etc/portage/package.mask:
> =www-client/chromium-8.0.552.0
>
> This case shows that, in fact, the mask comes first, as the atom in
> question is definitely unmasked in that scenario. I have tried
> putting
> either line into /etc/portage/profile/package.mask or .unmask, to no
> effect.
>
> I know I could do this by putting noninclusive comparative statements
> in
> .unmask, ala:
>
> <www-client/chromium-8.0.552.0
> >www-client/chromium-8.0.552.0
>
> But this seems somewhat clumsy to me. Does anyone know a trick to do
> what I'm looking for?
>
I usually comment out the line in package.unmask if I want the mask
to be effective. A line in /etc/portage/package.unmask overrules a
line in /etc/portage/package.mask .
Helmut.
prev parent reply other threads:[~2010-10-20 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 2:06 [gentoo-user] Which Comes First, the Unmask or the Mask? Andy Wilkinson
2010-10-20 14:28 ` Helmut Jarausch [this message]
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=1287584892.6107.0@numa-i \
--to=jarausch@igpm.rwth-aachen.de \
--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