public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alec Warner" <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Testing is not a valid reason to package.mask
Date: Thu, 2 Oct 2008 17:56:39 -0700	[thread overview]
Message-ID: <b41005390810021756i55006e62ga8909f1ed2ef5c@mail.gmail.com> (raw)
In-Reply-To: <20081002222435.35768855@epia.jer-c2.orkz.net>

On Thu, Oct 2, 2008 at 1:24 PM, Jeroen Roovers <jer@gentoo.org> wrote:
> # Gen 2 Developer <someone@gentoo.org> (`date`)
> # Masked for testing.
>>=rofl-cat/omgpkg-ver
>
>
> Please people,
>
>
>   if you want to get something tested, then don't mask it.If you find
> that you cannot commit an ebuild because of badly keyworded
> dependencies, then drop the relevant keywords and file a bug report
> with a KEYWORDREQ.

So you have made two comments.

1) 'Package.mask not for testing.'

2) 'If you cannot commit an ebuild due to badly keyworded deps; file
bugs to get them fixed.'

I agree with 2 but not with 1.

If pmask is not for testing...what is it for?

-Alec

>
>
> Kind regards,
>     JeR
>
>



  parent reply	other threads:[~2008-10-03  0:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02 20:24 [gentoo-dev] Testing is not a valid reason to package.mask Jeroen Roovers
2008-10-02 20:30 ` Jeroen Roovers
2008-10-02 20:41   ` Jeremy Olexa
2008-10-03  0:56 ` Alec Warner [this message]
2008-10-03  1:09   ` Josh Saddler
2008-10-03  2:14   ` Jeroen Roovers
2008-10-03  2:23     ` Dawid Węgliński
2008-10-03  3:16       ` Jeroen Roovers
2008-10-03  7:10         ` Alec Warner
2008-10-03 12:06           ` Thomas Sachau
2008-10-03 17:16             ` Alec Warner
2008-10-03  7:06 ` Mart Raudsepp
2008-10-03  9:29   ` [gentoo-dev] " Duncan
2008-10-04  5:44 ` Ryan Hill
2008-10-04 11:15   ` Thomas Anderson
2008-10-04 16:53   ` Michal Kurgan
2008-10-08  5:10   ` Iain Buchanan

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=b41005390810021756i55006e62ga8909f1ed2ef5c@mail.gmail.com \
    --to=antarus@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