From: Luke Maurer <maurerl@carleton.edu>
To: Spider <spider@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Why no local mask override? (PS)
Date: Fri, 20 Sep 2002 14:51:09 -0500 [thread overview]
Message-ID: <1032551469.684.8.camel@kryptonitespoon.res.carleton.edu> (raw)
In-Reply-To: <20020920131728.1cfe179f.spider@gentoo.org>
Sez Mike:
> solutions are being worked on to address. so the answer is
> 'its not done' ;)
> -mike
Ah. Okay, that's legit. :-)
Sez Spider:
> > for instance, if one is running GNOME 2 but using some GNOME 1.4 apps
> > (i.e. one is running GNOME 2), and one wants them to have a nice GTK1
> > theme, one has to unmask it.
>
> No, you just have to emerge the right version. the hierarchy in
> x11-themes/ has changed, look at how to emerge a specific version
> instead of unmasking.
Actually, it looks like things have changed since I last ran into this
problem: It used to be that emerge would refuse a masked ebuild even
when specified by filename. It looks like this is no longer the case -
meaning that, after all, there is an equivalent, though somewhat less
elegant, to a --nomask option. But I couldn't find mention of this in
the changelog; shouldn't this be more well-known? It would make for far
easier answers to all those "how to unmask such-and-such" posts.
Luke Maurer
maurerl@carleton.edu
P.S. I really don't mean to be a curmudgeon; this is merely a pet peeve.
Gentoo rocks.
next prev parent reply other threads:[~2002-09-20 19:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 15:17 [gentoo-dev] Why no local mask override? Luke Maurer
2002-09-20 4:08 ` mike
2002-09-20 11:17 ` [gentoo-dev] Why no local mask override? (PS) Spider
2002-09-20 19:51 ` Luke Maurer [this message]
2002-09-20 21:09 ` Spider
2002-09-21 2:35 ` Luke Maurer
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=1032551469.684.8.camel@kryptonitespoon.res.carleton.edu \
--to=maurerl@carleton.edu \
--cc=gentoo-dev@gentoo.org \
--cc=spider@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