Re: Superseded packages

[Ludovic Courtès]

Leo Famulari <address@hidden> 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’.