all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Superseded packages
Date: Sat, 10 Sep 2016 13:25:14 -0400	[thread overview]
Message-ID: <20160910172514.GA28562@jasmine> (raw)
In-Reply-To: <87vay8r9r3.fsf_-_@gnu.org>

On Tue, Sep 06, 2016 at 11:36:32PM +0200, Ludovic Courtès wrote:
> Hi!
> 
> ludo@gnu.org (Ludovic Courtès) skribis:
> 
> > I had an idea to use a ‘superseded’ entry in ‘properties’ that would
> > tell ‘guix package’ et al. to upgrade to the new package:
> >
> >   (package
> >     (name "attic")
> >     ;; …
> >     (properties `((superseded . ,borg))))
> 
> This is now implemented both at the package lookup level and in ‘guix
> package -u’ (the code is in 01afdab89c6a91f4cd05d3c4f4ff95a0402703eb 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.

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?

  reply	other threads:[~2016-09-10 17:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-04  2:12 Removing the attic package Leo Famulari
2016-09-04 13:10 ` ng0
2016-09-04 18:44   ` Leo Famulari
2016-09-05  8:20     ` Ludovic Courtès
2016-09-05  8:34       ` Ricardo Wurmus
2016-09-05  9:29       ` Efraim Flashner
2016-09-05 10:05         ` ng0
2016-09-05 10:20           ` ng0
2016-09-06 21:36       ` Superseded packages Ludovic Courtès
2016-09-10 17:25         ` Leo Famulari [this message]
2016-09-11 13:46           ` Ludovic Courtès
2016-09-11 15:19             ` Leo Famulari
2016-09-11 20:39               ` Ludovic Courtès
2016-09-20 21:18                 ` Leo Famulari
2016-09-24  2:14                   ` Ludovic Courtès
2016-09-25 16:42                     ` Leo Famulari
2016-09-26  9:44                       ` Efraim Flashner
2016-09-27 21:39                         ` Leo Famulari
2016-09-28  8:44                       ` Ludovic Courtès
2016-09-28 17:58                         ` Leo Famulari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160910172514.GA28562@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.