From: Christian Faulhammer <fauli@gentoo.org>
To: Gentoo Development <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Re: QA: package.mask policies
Date: Sat, 7 Nov 2009 19:33:12 +0100 [thread overview]
Message-ID: <20091107193312.5df04226@gentoo.org> (raw)
In-Reply-To: <20091107180322.GA23301@linux1>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
Hi,
William Hubbs <williamh@gentoo.org>:
> > * Masking live...
> > Heck no. This is not proper usage. Just use keywords mask.
> > KEYWORDS="". Problem solved and the package.mask is smaller. (Note,
> > in overlays do what ever you want, since it does not polute the
> > main mask from g-x86).
>
> True. If we mask live ebuilds with KEYWORDS="", there isn't a reason
> to put them in p.mask that I can think of.
Many users use "**" in their p.keywords file and get a live ebuild
then.
V-Li
--
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode
<URL:http://gentoo.faulhammer.org/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-11-07 18:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-07 17:24 [gentoo-dev] QA: package.mask policies Tomáš Chvátal
2009-11-07 18:03 ` William Hubbs
2009-11-07 18:33 ` Christian Faulhammer [this message]
2009-11-07 18:56 ` [gentoo-dev] " William Hubbs
2009-11-07 19:03 ` Duncan
2009-11-08 0:08 ` Nirbheek Chauhan
2009-11-08 1:25 ` Duncan
2009-11-08 23:46 ` Vlastimil Babka
2009-11-08 1:26 ` Kent Fredric
2009-11-08 15:13 ` Christian Faulhammer
2009-11-09 13:17 ` Duncan
2009-11-08 12:41 ` [gentoo-dev] " Peter Volkov
2009-11-08 16:57 ` Jeroen Roovers
2009-11-08 17:20 ` Tomáš Chvátal
2009-11-11 16:43 ` Jeroen Roovers
2009-11-11 17:11 ` [gentoo-dev] " Torsten Veller
2009-11-11 21:54 ` Jeroen Roovers
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=20091107193312.5df04226@gentoo.org \
--to=fauli@gentoo.org \
--cc=gentoo-dev@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