On Wed, May 04, 2016 at 04:05:50PM -0400, Ian Stakenvicius wrote
> On 04/05/16 03:43 PM, waltd...@waltdnes.org wrote:
> >
> > emerge --keyword-write
> >
> > ... similar to "emerge --autounmask-write", but have it write to
> > package.accept_keywords, rather than package.unmask?
> >
> > That wo
On 04/05/16 03:43 PM, waltd...@waltdnes.org wrote:
>
> emerge --keyword-write
>
> ... similar to "emerge --autounmask-write", but have it write to
> package.accept_keywords, rather than package.unmask?
>
> That would achieve the effect that people are looking for, with less
> work.
>
--auto
On Tue, May 03, 2016 at 09:46:10PM -0700, Matt Turner wrote
> On Tue, May 3, 2016 at 5:50 PM, Mike Gilbert wrote:
> > On Tue, May 3, 2016 at 5:34 PM, Jeroen Roovers wrote:
> >> The solution is to have people with an actual interest in a specific
> >> architecture determine whether stabilising a p
On Wed, May 4, 2016 at 8:44 AM, Mike Gilbert wrote:
> On Wed, May 4, 2016 at 10:41 AM, Peter Stuge wrote:
>> Mike Gilbert wrote:
>>> "doing your job"
>>
>> Remember that everyone is a volunteer.
>
> I am referring to arch testing as a job, because it only really works
> if people treat it that wa
On 05/04/2016 11:41 AM, Ian Stakenvicius wrote:
On 04/05/16 02:01 AM, Kent Fredric wrote:
On 4 May 2016 at 16:46, Matt Turner wrote:
Having built many stages for an "unstable" arch (mips) has taught me
one thing: it's awful being unstable-only. There's no end to the
compilation failures and
On Wed, May 4, 2016 at 10:41 AM, Peter Stuge wrote:
> Mike Gilbert wrote:
>> "doing your job"
>
> Remember that everyone is a volunteer.
I am referring to arch testing as a job, because it only really works
if people treat it that way. If stabilization does not take place in a
timely manner, the
On 04/05/16 02:01 AM, Kent Fredric wrote:
> On 4 May 2016 at 16:46, Matt Turner wrote:
>> Having built many stages for an "unstable" arch (mips) has taught me
>> one thing: it's awful being unstable-only. There's no end to the
>> compilation failures and other such headaches, none of which have
>>
Mike Gilbert wrote:
> "doing your job"
Remember that everyone is a volunteer.
> dropping stable keywords on everything but the bare necessities
Gentoo magically does a number of things which upstream never
intended and do not intentionally support. It is amazing, and
thank you so much to everyo
On Wed, May 4, 2016 at 12:46 AM, Matt Turner wrote:
> Having built many stages for an "unstable" arch (mips) has taught me
> one thing: it's awful being unstable-only. There's no end to the
> compilation failures and other such headaches, none of which have
> anything at all to do with the specifi
On 05/04/2016 06:46 AM, Matt Turner wrote:
> On Tue, May 3, 2016 at 5:50 PM, Mike Gilbert wrote:
>> On Tue, May 3, 2016 at 5:34 PM, Jeroen Roovers wrote:
>>> The solution is to have people with an actual interest in a specific
>>> architecture determine whether stabilising a package is viable, an
On 4 May 2016 at 16:46, Matt Turner wrote:
> Having built many stages for an "unstable" arch (mips) has taught me
> one thing: it's awful being unstable-only. There's no end to the
> compilation failures and other such headaches, none of which have
> anything at all to do with the specific archite
On Tue, May 3, 2016 at 5:50 PM, Mike Gilbert wrote:
> On Tue, May 3, 2016 at 5:34 PM, Jeroen Roovers wrote:
>> The solution is to have people with an actual interest in a specific
>> architecture determine whether stabilising a package is viable, and
>> taking sensible action, like dropping stabl
On Tue, May 3, 2016 at 5:34 PM, Jeroen Roovers wrote:
> The solution is to have people with an actual interest in a specific
> architecture determine whether stabilising a package is viable, and
> taking sensible action, like dropping stable keywords where applicable.
If these people do not actua
On Sun, 1 May 2016 16:16:59 -0700
Daniel Campbell wrote:
> On 05/01/2016 07:03 AM, Andreas K. Huettel wrote:
> > Am Sonntag, 1. Mai 2016, 15:32:27 schrieb Jeroen Roovers:
> >> On Sat, 30 Apr 2016 23:16:42 +0200
> >
> > (For the record, hppa is definitely NOT the problem.)
> >
> Forgive me
On Monday 02 of May 2016 16:43:01 you wrote:
| On Saturday 30 of April 2016 23:16:42 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 successfu
On Saturday 30 of April 2016 23:16:42 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 stabili
On 05/01/2016 07:03 AM, Andreas K. Huettel wrote:
> Am Sonntag, 1. Mai 2016, 15:32:27 schrieb Jeroen Roovers:
>> On Sat, 30 Apr 2016 23:16:42 +0200
>
> (For the record, hppa is definitely NOT the problem.)
>
Forgive me, I just pulled hppa out of the air as an example of a
secondary, different arc
On Sun, May 1, 2016 at 9:32 AM, Jeroen Roovers wrote:
> And it means we're missing opportunities where "pure" interpreted
> packages may test corner cases of the language implementation and find
> bugs in (JIT or previously) "compiled" code. And that means we're
> calling things "stable" that may
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Sonntag, 1. Mai 2016, 15:32:27 schrieb Jeroen Roovers:
> On Sat, 30 Apr 2016 23:16:42 +0200
>
> "Andreas K. Huettel" wrote:
> > just as a small reminder, to ease the load on all arch teams:
> >
> > If a stablerequest has the keyword ALLARCHES s
On Sat, 30 Apr 2016 23:16:42 +0200
"Andreas K. Huettel" wrote:
> 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
On 04/30/2016 07:26 PM, Rich Freeman wrote:
> On Sat, Apr 30, 2016 at 8:53 PM, Daniel Campbell wrote:
>>
>> 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.
>>
>
> The concept is that the m
On Sat, Apr 30, 2016 at 8:53 PM, Daniel Campbell wrote:
>
> 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.
>
The concept is that the maintainer will only use this when this is the
case. Th
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 stabilize
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
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 arch
25 matches
Mail list logo
