public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] QA Overlay Layout support.
Date: Sun, 1 Mar 2009 22:57:27 -0800	[thread overview]
Message-ID: <20090302065727.GD1955@comet> (raw)
In-Reply-To: <49AB7A52.3060401@gentoo.org>

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

On 19:18 Mon 02 Mar     , Alistair Bush wrote:
> Donnie Berkholz wrote:
>> Combine this with package.mask. To me, experimental means masked.
>
> Experimental within java means a lot of things,  or at least it should.  
> Anything from user contributed and non-dev qa'd to packages with bundled 
> jars to attempts to package projects like maven which are difficult and 
> time consuming ( and which attempts to do so have failed numerous times 
> before might I add ).
>
> Asking non-dev contributors to handle package.mask's would be a "less  
> than ideal". Resulting in "interesting breakages".  Currently by adding  
> java-experimental ( which might I add isn't available thru layman ) you  
> are accepting that risk.

I don't understand the distinction you're making here. Either way, users 
explicitly take a manual action to enable additional experimental 
packages (unmasking or adding an overlay full of them). In fact, I see 
the separate-overlay option as worse because then you get *everything* 
from the overlay, whereas package.mask is more granular and can be 
fine-tuned per-package.

Could you explain what you see as the important difference that makes 
package.mask bad and a separate overlay good?

-- 
Thanks,
Donnie

Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com

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

  reply	other threads:[~2009-03-02  6:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-24 22:59 [gentoo-dev] QA Overlay Layout support Alistair Bush
2009-01-26  4:59 ` Alistair Bush
2009-03-01 23:01 ` Jorge Manuel B. S. Vicetto
2009-03-02  3:11 ` Donnie Berkholz
2009-03-02  6:18   ` Alistair Bush
2009-03-02  6:57     ` Donnie Berkholz [this message]
2009-03-02  7:57       ` Alistair Bush
2009-03-02  9:29         ` Jorge Manuel B. S. Vicetto
2009-03-02 20:01           ` Wulf C. Krueger
2009-03-05  1:52             ` Jorge Manuel B. S. Vicetto
2009-03-06  9:55               ` Caleb Cushing
2009-03-03  7:19         ` Caleb Cushing
2009-03-03  7:43           ` [gentoo-dev] " Duncan
2009-03-03 10:56           ` [gentoo-dev] " Marijn Schouten (hkBst)
2009-03-03 12:42           ` Petteri Räty
2009-03-02 16:05     ` Thomas Sachau

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=20090302065727.GD1955@comet \
    --to=dberkholz@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