[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Guile 2.0.13
From: |
Ludovic Courtès |
Subject: |
Re: Guile 2.0.13 |
Date: |
Thu, 13 Oct 2016 23:11:38 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Leo Famulari <address@hidden> skribis:
> On Wed, Oct 12, 2016 at 10:13:32PM +0200, Ludovic Courtès wrote:
[...]
>> Yeah. I was thinking that we’d want to finish this core-updates cycle
>> and then later do an ungrafting round or something.
>>
>> WDYT?
>
> That sounds good. I think we should try doing some more specific
> "updates" branches in between releases, assuming we have the compute
> power and the motivation.
>
> And we could also have some periodic ungrafting rebuilds when necessary
> and feasible.
Yes, definitely.
More generally, we could try to have a “staging” branch for safe changes
that involve a rebuild of between ~300 and ~1200 packages, that we’d
merge more frequently than ‘core-updates’ (I think the Nix folks do
that). By “safe” I mean things like ungrafting, minor upgrades and
improvements; the goal would be to reduce the latency for such changes.
Things that rebuild more than ~1200 packages would still go to
‘core-updates’.
WDYT?
> So, we would graft guile-2.0, make guile-2.0/fixed use 2.0.12, and set
> replacement #f in guile-next? Anything else?
Yes, and a couple of related changes. Pushed as
c62a31ca802c2b225279c4b0360a4cfc2723ad28.
Thanks!
Ludo’.