Dnia 2014-06-30, o godz. 11:22:07
Ian Stakenvicius <a...@gentoo.org> napisał(a):

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> On 30/06/14 09:25 AM, Rich Freeman wrote:
> > On Mon, Jun 30, 2014 at 12:01 AM, William Hubbs
> > <willi...@gentoo.org> wrote:
> >> 
> >> On Sun, Jun 29, 2014 at 10:04:54AM -0400, Rich Freeman wrote:
> >>> On Sun, Jun 29, 2014 at 8:36 AM, hasufell <hasuf...@gentoo.org>
> >>> wrote:
> >>>> This is still too vague for me. If it's expected to be
> >>>> short-term, then it can as well just land in ~arch.
> >>> 
> >>> A package that hasn't been tested AT ALL doesn't belong in
> >>> ~arch. Suppose the maintainer is unable to test some aspect of
> >>> the package, or any aspect of the package?  Do we want it to
> >>> break completely for ~arch?  In that event, nobody will run
> >>> ~arch for that package, and then it still isn't getting
> >>> tested.
> >> 
> >> 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.
> > 
> > Agree 100%.  I'm taking about masking things that HAVEN'T BEEN
> > TESTED AT ALL.  The maintainer knows that they compile, and that is
> > it.  Or maybe they tested it in a very limited set of circumstances
> > but know that other untested circumstances are important to the
> > users and they have definite plans to get them tested.
> > 
> 
> 
> Here's a great example of this -- dev-libs/nss-3.16-r1 is p.masked by
> me for testing, because when I converted it to multilib i needed to
> change the way it does some internal ABI determination tests, and
> although I know it does work fine on multilib-amd64 and (non-multilib)
> x86, I am not confident without more testing that it will work for
> cross-compiles or other non-multilib arches.  As such, it -is- in the
> tree, but I've masked it until I can test it myself in these
> circumstances or find someone else that can do it for me.

But... if you unmask it, someone will test it and report whether it
works :P.

-- 
Best regards,
Michał Górny

Attachment: signature.asc
Description: PGP signature

Reply via email to