From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Transition to /gnu/store Date: Wed, 12 Mar 2014 12:06:10 +0100 Message-ID: <87vbvjllr1.fsf@gnu.org> References: <87eh2myiqy.fsf@gnu.org> <87y50qlzmx.fsf@yeeloong.lan> <87fvmxrj21.fsf_-_@gnu.org> <87r46b7yvu.fsf@gnu.org> <20140310141806.GB9152@debian.univ-mrs.fr> <874n35n74v.fsf@gnu.org> <531E1C87.9030005@gmail.com> <87zjkxiwt9.fsf@gnu.org> <20140312083514.GA8869@debian.univ-amu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53762) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WNgzK-0004IS-VL for guix-devel@gnu.org; Wed, 12 Mar 2014 07:06:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WNgzF-0007w2-4X for guix-devel@gnu.org; Wed, 12 Mar 2014 07:06:18 -0400 Received: from hera.aquilenet.fr ([2a01:474::1]:58991) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WNgzE-0007vx-U1 for guix-devel@gnu.org; Wed, 12 Mar 2014 07:06:13 -0400 In-Reply-To: <20140312083514.GA8869@debian.univ-amu.fr> (Andreas Enge's message of "Wed, 12 Mar 2014 09:35:14 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Andreas Enge Cc: guix-devel@gnu.org Andreas Enge skribis: > Nothing prevents us from merging core-updates several times before a rele= ase. > As I see it, core-updates is there so that people tracking git master are= not > forced to recompile too often. Too often and too much. Also, changes in core-updates can potentially break more stuff. > But a change to master that forces recompilat- ion should be linked > with a merge of core-updates into master, which comes "for free" at > this moment. Right, but in master we don=E2=80=99t change =E2=80=9Ccore=E2=80=9D stuff l= ike build/utils.scm, glibc, etc. Sometimes there are changes that trigger a lot of rebuild, but never as much as what we do in core-updates. Now, I agree we must find a way to avoid core-updates to last for too long. That probably means we need to agree on a time-based policy. Ideally, we=E2=80=99d make a new release every two months (we=E2=80=99re la= te this time), and thus have a core-updates branch living in between two releases. How does that sound? Thanks, Ludo=E2=80=99.