From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Removing the attic package
Date: Mon, 5 Sep 2016 12:29:56 +0300 [thread overview]
Message-ID: <20160905092956.GC23794@macbook42.flashner.co.il> (raw)
In-Reply-To: <87d1kirc4r.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]
On Mon, Sep 05, 2016 at 10:20:36AM +0200, Ludovic Courtès wrote:
> Hi!
>
> Leo Famulari <leo@famulari.name> skribis:
>
> >
> > 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’.
>
I think it makes sense to change the description that this package is
slated for eventual removal. Another example is pinentry. We now have 4
pinentry packages, and the original pinentry package just points to
pinentry-gtk. I think it would make sense in that case to change the
description to something like `the pinentry package in guix is
depreciated, please remove it and install pinentry-gtk to retain the
same functinality' or something along those lines.
In this case something about attic having serious unpatched flaws, is
unmaintained, and that borg is a fork & continuation of it, would be a
good change.
That might keep new people from installing it, but how would we get
people who have already installed it to uninstall it? Or to see the
message?
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-09-05 9:30 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 [this message]
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=20160905092956.GC23794@macbook42.flashner.co.il \
--to=efraim@flashner.co.il \
--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.