From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Superseded packages
Date: Sun, 11 Sep 2016 22:39:08 +0200 [thread overview]
Message-ID: <87bmzujhn7.fsf@gnu.org> (raw)
In-Reply-To: <20160911151945.GB6400@jasmine> (Leo Famulari's message of "Sun, 11 Sep 2016 11:19:45 -0400")
Leo Famulari <leo@famulari.name> skribis:
> On Sun, Sep 11, 2016 at 03:46:34PM +0200, Ludovic Courtès wrote:
>> > 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 ‘attic’ command, which would make it incompatible by default, we
>> may want to change the Borg package to include such a command.
>
> There are other incompatibilities, for example in the repository format.
> Borg provides a `borg upgrade` tool that performs a one-way conversion
> of Attic repos to Borg repos. Just creating an 'attic -> borg' alias
> would not be enough; any automated backup scripts would still fail.
Then I don’t know. Either we mark Attic as superseded by Borg anyway,
or we need another mechanism to mark a package as “discouraged”?
Ludo’.
next prev parent reply other threads:[~2016-09-11 20:39 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
2016-09-11 13:46 ` Ludovic Courtès
2016-09-11 15:19 ` Leo Famulari
2016-09-11 20:39 ` Ludovic Courtès [this message]
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=87bmzujhn7.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.