-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>> ex.
>>
>> gcc 4.1.1 works on x86 with the following:
>>
>> USE="gtk nls -bootstrap -build -doc -fortran -gcj -hardened -ip28
>> -ip32r10k -mudflap -multislot -nocxx -objc -objc++ -objc-gc -test
>> -vanilla"
>
> Looks OK to me. But hey, aren't arch devs and testers alike supposed to
> test (almost) all flags? And also, wouldn't you also want to know about
> FEATURES, specifically FEATURES='{test,collision-detect}'? How about
> KEYWORDS? You would still need to be able to find the full `emerge info`
> in an attachment, I guess.
Heck no, I'd spend a few weeks just testing for example php. That's
deranged at its best and insane at the worst. The request as put out
to the arch testers is to use the system like they use any system,
just that they only run x86, amd64 other packages except for what they
are going to be testing. As far as features go we ask that they run
the same as a developer should, test collision-protect on top of what
is already added by default. Keywords is not useful for the arch teams
as we know that the AT's run $arch and not ~$arch. However at least
saying x86 okie with me here would be a requirement
>
> I still think failures should be reported in separate bugs, as they are
> likely to cause lots more information to be passed.
>
>
> Kind regards,
> JeR
Actually, one thing that you might not know is that quite a few of the
archtesters are capable programmers, they've tested a build that
failed and went about submitting a patch that would fix the issue
right there on the stabilization bug. Now you might want to say why
are they not developers yet. Part of that is probably, because they
haven't been approached by a developer yet, the second is that some
can't dedicate more time then what they are doing currently to help
the project, and that is alright. They are helping the arch teams
immensely and I'm thankful for them taking their own time to be doing
what they are doing. I might not always say thank you on the bugs,
however I feel it everyday.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFE3K8uSENan+PfizARAlacAJ4mb/pTvX119A+41a0qVG8SE3IrcQCfaOSn
iMxOOBGJCXGxZfU+4BeB3Zg=
=fbsi
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
