Re: [gentoo-dev] package.mask vs ~arch

["Andreas K. Huettel" <dilfridge@gentoo.org>]

[-- Attachment #1: Type: Text/Plain, Size: 1258 bytes --]

Am Montag, 30. Juni 2014, 06:01:53 schrieb William Hubbs:
> 
> I'm not saying that we should just randomly throw something into ~arch
> without testing it, but ~arch users are running ~arch with the
> understanding that their systems will break from time to time and they
> are expected to be able to deal with it when/if it happens. ~arch is
> not a second stable branch.
> 

Hey William, 

here's my take:

Masked commit:
* a part of a bigger version bump, i.e. one of many packages that need to 
update together
* or something where I *know* that issues preventing normal function still 
exist. I.e., I want to be able to ask others for testing, but something is 
still missing and I'm actively working on it.

~arch commit: 
* I'm reasonably sure that it should work; it works for me.

Now, one can argue that work in progress should go into an overlay. That in my 
opinion makes sense for e.g. kde packages and kde overlay, or qt packages and 
qt overlay, or similar. Making a fresh overlay for one package or asking to 
add my dev overlay for one required ebuild makes no sense. 

Only my opinion...
Cheers, Andreas


-- 

Andreas K. Huettel
Gentoo Linux developer 
dilfridge@gentoo.org
http://www.akhuettel.de/


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 966 bytes --]