Re: Dealing with mass rebuilds

[Efraim Flashner]

On Tue, 20 Oct 2015 21:45:54 +0200
address@hidden (Ludovic Courtès) wrote:

> Mark H Weaver <address@hidden> skribis:
> 
> > Andreas Enge <address@hidden> writes:
> >  
> >> andreas pushed a commit to branch master
> >> in repository guix.
> >>
> >> commit 075c3ebd2dc3d8223e23025ceb5026810dfaa98d
> >> Author: Andreas Enge <address@hidden>
> >> Date:   Sun Oct 18 12:20:02 2015 +0200
> >>
> >>     gnu: curl: Update to 7.45.0.  
> >
> > To avoid unnecessary rebuilds on hydra, I reverted this commit on
> > master, and instead pushed it to the 'dbus-update' branch, which will
> > hopefully be merged soon.  
> 
> We’re talking of ~150 dependent packages, which to me sounded OK¹.
> 
> If we delay obvious changes like this too much, the risk is to end up
> with upgrade-everything branches that take ages to get merged (what is
> happening with ‘dbus-update’.)
> 
> The Nixpkgs folks have a ‘staging’ branch for changes that cause mass
> rebuilds but are well tested, such that they can be merged into ‘master’
> anytime².  Perhaps something we should do as well?
> 
> Ludo’.
> 
> ¹ https://lists.gnu.org/archive/html/guix-devel/2015-10/msg00653.html
> ² http://comments.gmane.org/gmane.linux.distributions.nixos/13447
> 

It would make an obvious place to push an sqlite update and allow the
dbus-update update branch to focus just on the dbus-update, or a core-update
branch to focus just on core updates.

-- 
Efraim Flashner   <address@hidden>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

pgppnoMJebSpk.pgp
Description: OpenPGP digital signature