public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kent Fredric <kentfredric@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: QA: package.mask policies
Date: Sun, 8 Nov 2009 14:26:25 +1300	[thread overview]
Message-ID: <8cd1ed20911071726k7d2817fcn66b2db3851b7d37d@mail.gmail.com> (raw)
In-Reply-To: <8b4c83ad0911071608n7ebc31dcy6e7eb1d9470b3067@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2050 bytes --]

On Sun, Nov 8, 2009 at 1:08 PM, Nirbheek Chauhan <nirbheek@gentoo.org>wrote:

> On Sun, Nov 8, 2009 at 12:33 AM, Duncan <1i5t5.duncan@cox.net> wrote:
> > 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! =:^]
> >
>
> We had something interesting happen with policykit. It was masked for
> a very long time, and so all users of policykit had
> "sys-auth/policykit" in p.unmask. Then it was unmasked, but of course
> who bothers cleaning up their local configuration as long as it works?
>
> Months later, policykit-0.92 was added (masked) which was ABI, API,
> UI, everything incompatible. Naturally portage on said users' boxes
> was very happy to see such an update on the system and it very
> promptly upgraded policykit.
>
> And of course it completely hosed everything on top of X.
>
> We received bug reports for this a *long* time after adding it. After
> getting sick of duping, and since the new ebuild was broken in a few
> ways too (and we had decided to rename policykit-0.92 it to
> sys-auth/polkit), we finally decided to remove it.
>
> Lesson to be learnt: users are morons with short attention spans[1].
> But we cannot ignore that fact.
>
>
>
In such cases users should be using version specific/version ranges for
p.keywords/p.unmask.

I don't recall seeing much literature on this practice though with regards
to standard recommendations of users and how they should use their own
p.keywords and p.unmask.

Maybe a good standard practice would be to *not* use ranged p.masks and have
explicit =version p.masks, so that users who use the commonly available
scripts that just copy from p.mask  to p.unmask don't get silently bitten as
a consequence.

-- 
Kent

perl -e  "print substr( \"edrgmaM  SPA NOcomil.ic\\@tfrken\", \$_ * 3, 3 )
for ( 9,8,0,7,1,6,5,4,3,2 );"

http://kent-fredric.fox.geek.nz

[-- Attachment #2: Type: text/html, Size: 2622 bytes --]

  parent reply	other threads:[~2009-11-08  1:26 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
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 [this message]
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=8cd1ed20911071726k7d2817fcn66b2db3851b7d37d@mail.gmail.com \
    --to=kentfredric@gmail.com \
    --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