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