From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Superseded packages Date: Sun, 11 Sep 2016 15:46:34 +0200 Message-ID: <87a8felfb9.fsf@gnu.org> References: <20160904021256.GA21539@jasmine> <874m5vvmi8.fsf@we.make.ritual.n0.is> <20160904184416.GB29947@jasmine> <87d1kirc4r.fsf@gnu.org> <87vay8r9r3.fsf_-_@gnu.org> <20160910172514.GA28562@jasmine> 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]:54626) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bj55l-0005fq-7C for guix-devel@gnu.org; Sun, 11 Sep 2016 09:46:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bj55h-00054x-24 for guix-devel@gnu.org; Sun, 11 Sep 2016 09:46:40 -0400 In-Reply-To: <20160910172514.GA28562@jasmine> (Leo Famulari's message of "Sat, 10 Sep 2016 13:25:14 -0400") 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" To: Leo Famulari Cc: guix-devel@gnu.org Hello! Leo Famulari skribis: > On Tue, Sep 06, 2016 at 11:36:32PM +0200, Ludovic Court=C3=A8s wrote: >> Hi! >>=20 >> ludo@gnu.org (Ludovic Court=C3=A8s) skribis: >>=20 >> > I had an idea to use a =E2=80=98superseded=E2=80=99 entry in =E2=80=98= properties=E2=80=99 that would >> > tell =E2=80=98guix package=E2=80=99 et al. to upgrade to the new packa= ge: >> > >> > (package >> > (name "attic") >> > ;; =E2=80=A6 >> > (properties `((superseded . ,borg)))) >>=20 >> This is now implemented both at the package lookup level and in =E2=80= =98guix >> package -u=E2=80=99 (the code is in 01afdab89c6a91f4cd05d3c4f4ff95a04027= 03eb and >> an example is in 967cfd18f666f24ae9cbad14ea8e6921c10cba81): > > This is nice :) > > In 56ab55d1df I used it to properly replace the old letsencrypt package > with certbot. > > In this case, I had already made letsencrypt inherit from certbot some > months ago. I wanted letsencrypt users to get the latest version of the > software from the EFF team, and presumably users have since fixed the > breakage caused by the executable name change. Now, their profiles will > finally stop including a letsencrypt package as they upgrade, and I plan > to remove the letsencrypt variable completely after a couple more > certbot releases. > > I think using this mechanism is appropriate in this case because > letsencrypt / certbot are from the same team. Basically it's the same > software, with 's/letsencrypt/certbot/g' applied to the codebase. This is definitely the target use case. > I'm not sure about Attic / Borg. Superseding attic will break > automation, although I did that when I made letsencrypt inherit from > certbot. Also, the authors are different. Advice? I would make Borg supersede Attic. However, if Borg does not provide, say, an =E2=80=98attic=E2=80=99 command, which would make it incompatible b= y default, we may want to change the Borg package to include such a command. WDYT? Ludo=E2=80=99.