public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] old "masked for testing" entries
Date: Mon, 30 Jun 2014 16:22:49 -0500	[thread overview]
Message-ID: <20140630212249.GA3345@linux1> (raw)
In-Reply-To: <CAJ0EP40q1ShZtcajX2g4d6ex+NfmCC_9dQ0F-DdqmFGe2UOPMQ@mail.gmail.com>

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

On Mon, Jun 30, 2014 at 04:46:04PM -0400, Mike Gilbert wrote:
> On Mon, Jun 30, 2014 at 12:38 PM, William Hubbs <williamh@gentoo.org> wrote:
> > All,
> >
> > Rich Freeman asked, in another thread, for specific examples of old
> > package.mask entries that just have "masked for testing" as the
> > description.
> >
> > Here is what I found with a quick look through package.mask. These
> > should be cleaned up by either 1) removing the mask or 2) booting the
> > affected packages or versions from the tree.
> >
> 
> Or 3) Improve the mask message.
>
> For example, I think  the major reason for the sys-libs/db mask is a
> weird licensing issue. It's still nice to have it in the tree.

If there is a weird licensing issue, it would be better to get
the answers needed to resolve that issue and remove the mask.

p.mask should never be permanent.

William

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-06-30 21:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-30 16:38 [gentoo-dev] old "masked for testing" entries William Hubbs
2014-06-30 20:46 ` Mike Gilbert
2014-06-30 21:22   ` William Hubbs [this message]
2014-06-30 21:40   ` James Cloos
2014-06-30 21:56     ` Kristian Fiskerstrand
2014-06-30 23:11       ` James Cloos
2014-06-30 21:58     ` Michał Górny
2014-06-30 22:02       ` James Cloos

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=20140630212249.GA3345@linux1 \
    --to=williamh@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