public inbox for gentoo-qa@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alec Warner" <antarus@gentoo.org>
To: gentoo-qa@lists.gentoo.org
Cc: "Steve Dibb" <beandog@gentoo.org>
Subject: Re: [gentoo-qa] splitting up package.mask
Date: Fri, 14 Mar 2008 07:54:28 -0700	[thread overview]
Message-ID: <b41005390803140754o6b54c93bve27fa69271987170@mail.gmail.com> (raw)
In-Reply-To: <200803140651.15897.vapier@gentoo.org>

On 3/14/08, Mike Frysinger <vapier@gentoo.org> wrote:
> On Thursday 13 March 2008, Steve Dibb wrote:
>  > Because package.mask in CVS for profiles is so huge, I think it might
>  > help it to get organized if we split it up a bit.
>  >
>  > halcyon had a good idea for the scheme: testing, broken, removal.  That
>  > seems to sum up the main 3 reason that a package would be masked.
>  >
>  > Right now there are 679 entries in package.mask.  The reason I came up
>  > with the idea was to find a way to make it easier for treecleaners to
>  > quickly see which ones they were working on.
>  >
>  > I'd like to take the discussion to -dev but wanted to get QA's thoughts
>  > first.  I haven't looked into whether or not this is technically
>  > feasible at all.
>
>
> i think the real solution here is allowing masking in a package
>
> -mike
>
>

You want to add a metadata key and cache it you mean?

-Alec
-- 
gentoo-qa@lists.gentoo.org mailing list



  reply	other threads:[~2008-03-14 14:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14  2:59 [gentoo-qa] splitting up package.mask Steve Dibb
2008-03-14  3:06 ` Alec Warner
2008-03-14  7:12 ` Marius Mauch
2008-03-14 20:54   ` Chris Gianelloni
2008-03-15  1:50     ` Mark Loeser
2008-03-14 10:51 ` Mike Frysinger
2008-03-14 14:54   ` Alec Warner [this message]
2008-03-15  3:03     ` Mike Frysinger

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=b41005390803140754o6b54c93bve27fa69271987170@mail.gmail.com \
    --to=antarus@gentoo.org \
    --cc=beandog@gentoo.org \
    --cc=gentoo-qa@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