| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 30/06/14 09:25 AM, Rich Freeman wrote: |
| 5 |
> On Mon, Jun 30, 2014 at 12:01 AM, William Hubbs |
| 6 |
> <williamh@g.o> wrote: |
| 7 |
>> |
| 8 |
>> On Sun, Jun 29, 2014 at 10:04:54AM -0400, Rich Freeman wrote: |
| 9 |
>>> On Sun, Jun 29, 2014 at 8:36 AM, hasufell <hasufell@g.o> |
| 10 |
>>> wrote: |
| 11 |
>>>> This is still too vague for me. If it's expected to be |
| 12 |
>>>> short-term, then it can as well just land in ~arch. |
| 13 |
>>> |
| 14 |
>>> A package that hasn't been tested AT ALL doesn't belong in |
| 15 |
>>> ~arch. Suppose the maintainer is unable to test some aspect of |
| 16 |
>>> the package, or any aspect of the package? Do we want it to |
| 17 |
>>> break completely for ~arch? In that event, nobody will run |
| 18 |
>>> ~arch for that package, and then it still isn't getting |
| 19 |
>>> tested. |
| 20 |
>> |
| 21 |
>> I'm not saying that we should just randomly throw something into |
| 22 |
>> ~arch without testing it, but ~arch users are running ~arch with |
| 23 |
>> the understanding that their systems will break from time to time |
| 24 |
>> and they are expected to be able to deal with it when/if it |
| 25 |
>> happens. ~arch is not a second stable branch. |
| 26 |
> |
| 27 |
> Agree 100%. I'm taking about masking things that HAVEN'T BEEN |
| 28 |
> TESTED AT ALL. The maintainer knows that they compile, and that is |
| 29 |
> it. Or maybe they tested it in a very limited set of circumstances |
| 30 |
> but know that other untested circumstances are important to the |
| 31 |
> users and they have definite plans to get them tested. |
| 32 |
> |
| 33 |
|
| 34 |
|
| 35 |
Here's a great example of this -- dev-libs/nss-3.16-r1 is p.masked by |
| 36 |
me for testing, because when I converted it to multilib i needed to |
| 37 |
change the way it does some internal ABI determination tests, and |
| 38 |
although I know it does work fine on multilib-amd64 and (non-multilib) |
| 39 |
x86, I am not confident without more testing that it will work for |
| 40 |
cross-compiles or other non-multilib arches. As such, it -is- in the |
| 41 |
tree, but I've masked it until I can test it myself in these |
| 42 |
circumstances or find someone else that can do it for me. |
| 43 |
|
| 44 |
|
| 45 |
-----BEGIN PGP SIGNATURE----- |
| 46 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 47 |
|
| 48 |
iF4EAREIAAYFAlOxgJ8ACgkQ2ugaI38ACPC8zAD/XwulPJp4f3xNFe4ZP7gE+kmp |
| 49 |
qhmdvJjUFyWW8j1dTHMA/jFc/mrH/dnyq/MJWBlUbEFY3ccebpLw/8C6/IaSeXw4 |
| 50 |
=iKL1 |
| 51 |
-----END PGP SIGNATURE----- |
Archives