all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Removing the attic package
Date: Mon, 05 Sep 2016 10:20:36 +0200	[thread overview]
Message-ID: <87d1kirc4r.fsf@gnu.org> (raw)
In-Reply-To: <20160904184416.GB29947@jasmine> (Leo Famulari's message of "Sun, 4 Sep 2016 14:44:16 -0400")

Hi!

Leo Famulari <leo@famulari.name> skribis:

> I don't want to steer new users towards this broken software, and I
> think removing the package is a safe choice. Current Attic users could
> continue to use it, because it won't be removed from their profile
> unless they do `guix package --remove attic`.

Since, AIUI, Borg is a compatible “continuation” of Attic, it makes
sense to remove Attic.

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))))

ENOSYS, though.

> And Borg can convert Attic repos for users who are interested in
> moving on, so these users will not lose access to their data even if
> they do uninstall Attic on their machines.
>
> Do we have any guidelines about "retiring" packages?

Not yet!

Of course there’s a fine line here: we cannot systematically retire
packages “just” because they have bugs (all of them do ;-)).  So we have
to be cautious.  In this case, it can be considered a serious bug in the
package’s core functionality, *and* there’s a fix provided by a fork, so
I see no obstacle in removing it.

What do people think?

Thanks,
Ludo’.

  reply	other threads:[~2016-09-05  8:20 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 [this message]
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
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=87d1kirc4r.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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.