From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Hinsen Subject: bug#22629: =?UTF-8?Q?=E2=80=9CStable=E2=80=9D?= branch Date: Thu, 30 Aug 2018 16:46:43 +0200 Message-ID: References: <87vb5vsffd.fsf@gnu.org> <87pny2iks2.fsf@gnu.org> <877ekagtg9.fsf@netris.org> <87zhx5msfl.fsf@pompo.co> <87lg8pccys.fsf_-_@netris.org> <87zhx59gh3.fsf@elephly.net> <875zzs9wzl.fsf@netris.org> <874lfcxd2v.fsf_-_@gnu.org> 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]:36458) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fvODy-0001Dk-Tg for bug-guix@gnu.org; Thu, 30 Aug 2018 10:47:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fvODv-0000Fx-HQ for bug-guix@gnu.org; Thu, 30 Aug 2018 10:47:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:34281) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fvODv-0000FX-Ch for bug-guix@gnu.org; Thu, 30 Aug 2018 10:47:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fvODu-0001ko-4N for bug-guix@gnu.org; Thu, 30 Aug 2018 10:47:03 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <874lfcxd2v.fsf_-_@gnu.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= , Alex Sassmannshausen Cc: 22629@debbugs.gnu.org Hi Ludo and Alex, ludo@gnu.org (Ludovic Court=C3=A8s) writes: > These are all things that very rarely, if ever, changed over the last 5 > years. I expect the change rate to remain the same. :-) That's reassuring! > You seem to be arguing of a =E2=80=9Cstable=E2=80=9D branch in the sense = that the Guix > tools (the CLI in particular) wouldn=E2=80=99t change much, is that corre= ct? > > I=E2=80=99m asking because there are several ways to define =E2=80=9Cstab= le.=E2=80=9D Initially > I thought what you had in mind was like the =E2=80=9Cstable=E2=80=9D bran= ch in Debian, > meaning that packages only get security updates. To me that=E2=80=99s a > different thing. What I have in mind is whatever it takes to build a stable software system. That includes stable ingredients (packages) but also stable glue, meaning the package definitions and the build system that produces the binaries from them. Stability of the Guix CLI is much less relevant from my point of view. Alex Sassmannshausen writes: > I don't know if this is what Konrad desires, but from my perspective, a > desirable part of the definition of stable would be a that the build > farms have produced a set of binaries/substitutes for a given Guix > revision that is "good enough". That's another very practically relevant notion of stability. Mine goes beyond that though. For example, I'd require all packages to build and pass tests at all times. Konrad.