Saturday 19 Sep 2015 09:55:14, Anthony G. Basile wrote : > On 9/19/15 8:56 AM, Ian Stakenvicius wrote: > > Sent from an iPhone, sorry for the HTML... > > > > On Sep 19, 2015, at 8:31 AM, Vadim A. Misbakh-Soloviov <[email protected]> > > wrote: > > > >>> So, if an arch developer tests the package(s) on one architecture, he is > >>> allowed to stabilize/keyword for all. > >> And how about the > >>> some arches rquires additional tests during stabilization, like so: mips*, > >> arm*, and some more exotic ones > >> definition in developer manuals? :) > >> > >> -- > >> Best regards, > >> mva > > The ALLARCHES keyword is meant for stuff that is essentially > > platform-agnostic. Python code shouldn't act any different on arm than > > arm64 than amd64. Using that keyword on something like ffmpeg would be a > > bad use of the keyword. > > Even with python where, for example, `import ctypes' might trigger > something on one arch and not another. Anyhow, thanks for the reminder > ago. I see that keyword as "risky" but an unfortunate risk we have to > take because we are short of manpower and don't have automated arch > testing. I say use it where it appears reasonable (eg interpreted > script and not compiled code) but be ready that every once in a while > we'll get bitten. > > -- > Anthony G. Basile, Ph.D. > Gentoo Linux Developer [Hardened] > E-Mail : [email protected] > GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA > GnuPG ID : F52D4BBA > >
We've been using this keyword fairly often (we = Gentoo Java team) whenever possible since the announcement and it worked out pretty well so far. -- Patrice Clement Gentoo Linux developer http://www.gentoo.org
