Leo Famulari <l...@famulari.name> skribis: > On Sun, Sep 11, 2016 at 10:39:08PM +0200, Ludovic Courtès wrote: >> > 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”? > > I've attached a patch that marks Attic as superseded by Borg. I'd like > to put it on core-updates. That way, we can mention it in the release > notes of the next Guix release, and hopefully people will notice the > change. > > WDYT?
I think it could even go to ‘master’, but yes, we should mention it in the next release notes. > From 374f81963d3ba4ec4a5e48c12848032ca8085aaf Mon Sep 17 00:00:00 2001 > From: Leo Famulari <l...@famulari.name> > Date: Tue, 20 Sep 2016 16:59:59 -0400 > Subject: [PATCH] gnu: attic: Superseded by borg. > > * gnu/packages/backup.scm (attic): Superseded by borg. > * gnu/packages/python.scm (python-llfuse-0.41): Remove variable. [...] > +(define-public attic > + (package (inherit borg) > + (name "attic") > + (properties `((superseded . ,borg))))) I was thinking that we could keep the ‘attic’ recipe as-is, only with this extra ‘properties’ field. That way, “guix package -u” and “guix package -i attic” would install Borg, but people who insist could still run: guix package -e '(@ (gnu packages backup) attic)' Thoughts? Anyway, feel free to push whichever sounds best to you! Thanks, Ludo’.
