public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: QA: package.mask policies
Date: Sat, 7 Nov 2009 19:03:47 +0000 (UTC)	[thread overview]
Message-ID: <pan.2009.11.07.19.03.45@cox.net> (raw)
In-Reply-To: 20091107193312.5df04226@gentoo.org

Christian Faulhammer posted on Sat, 07 Nov 2009 19:33:12 +0100 as
excerpted:

> 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.

There's two different ways of seeing that.

1) Users using ** in their package.keywords file should know enough about 
what they're doing to use their own package.mask, as well.  If they're 
using ** in the keywords file, they're /saying/ they're reading to handle 
such things, after all, why shouldn't we let them?

2) That won't necessarily stop the bugs from rolling in.  Some devs may 
get tired of live pkg bugs and package.mask it, thus putting up a double-
barrier to the live ebuild.  If users jump BOTH barriers and fall over 
the ledge, well... maybe they /need/ that Darwin Award! =:^]

Thus I can see either way.  If a dev's sick of dealing with live package 
bugs, maybe a package.mask will keep a few more folks from jumping over 
that ledge and filing them.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman




  parent reply	other threads:[~2009-11-07 19:04 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   ` [gentoo-dev] " Christian Faulhammer
2009-11-07 18:56     ` William Hubbs
2009-11-07 19:03     ` Duncan [this message]
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=pan.2009.11.07.19.03.45@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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