[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev] Reminder: ALLARCHES
From:       Matthew Thode <prometheanfire () gentoo ! org>
Date:       2016-05-01 1:15:16
Message-ID: 572558A4.6070504 () gentoo ! org
[Download RAW message or body]


On 04/30/2016 07:53 PM, Daniel Campbell wrote:
> On 04/30/2016 02:16 PM, Andreas K. Huettel wrote:
>>
>> Hi all,
>>
>> just as a small reminder, to ease the load on all arch teams:
>>
>> If a stablerequest has the keyword ALLARCHES set, then
>> * the first arch that tests successfully and stabilizes
>> * can and *should* immediately stabilize for all requested arches!
>>
>> Whether this keyword is set on a bug is decision of the package maintainer.
>>
>> For example, Perl team sets ALLARCHES normall for all pure-perl packages
>> (i.e., no compilation / gcc involved).
>>
>> Here's an example how this was used:
>> https://bugs.gentoo.org/show_bug.cgi?id=578408
>> https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=44c2d31dfc61bb3e2aee3709cb5a784b213511fa
>>
>> Cheers, Andreas
>>
>>
> 
> A package working on one arch won't necessarily guarantee that it works
> correctly on all other arches. Shouldn't we at least make sure we're
> testing on the relevant arch? For example, I don't have any hppa
> hardware. If I stabilized for amd64, why should I stabilize for hppa? I
> can't in good faith claim that it'll work fine for hppa because I've not
> tested it.
> 
> As you said, however, it's a choice of the maintainer. Things like Perl
> and Python may be less prone to this issue since they're meant to be
> portable.
> 
> My apologies if my concern is misplaced.
> 
> ~zlg
> 
Yes, this is mainly for interpreted languages (python/perl/ruby/etc)

-- 
-- Matthew Thode (prometheanfire)


["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]