On Wed, Sep 28, 2016 at 10:44:26AM +0200, Ludovic Courtès wrote:
> Leo Famulari skribis:
> > So the attached patch moves attic after borg and supersedes it. Is it
> > expected that we have to shuffle the package definition around like
> > this?
>
> Yes, because ‘properties’ are evaluated eagerly.
Leo Famulari skribis:
> On Sat, Sep 24, 2016 at 11:14:41AM +0900, Ludovic Courtès wrote:
>> Leo Famulari skribis:
>> > +(define-public attic
>> > + (package (inherit borg)
>> > +(name "attic")
>> > +(properties `((superseded . ,borg)
>>
>> I was thinking that we could keep the ‘att
On Mon, Sep 26, 2016 at 12:44:41PM +0300, Efraim Flashner wrote:
> On Sun, Sep 25, 2016 at 12:42:08PM -0400, Leo Famulari wrote:
> > I found that I had to move the attic package definition below borg's, or
> > else the borg variable was unbound when building (gnu packages backup):
> shot in the da
On Sun, Sep 25, 2016 at 12:42:08PM -0400, Leo Famulari wrote:
> On Sat, Sep 24, 2016 at 11:14:41AM +0900, Ludovic Courtès wrote:
> > Leo Famulari skribis:
> > > +(define-public attic
> > > + (package (inherit borg)
> > > +(name "attic")
> > > +(properties `((superseded . ,borg)
> >
>
On Sat, Sep 24, 2016 at 11:14:41AM +0900, Ludovic Courtès wrote:
> Leo Famulari skribis:
> > +(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
> thi
Leo Famulari 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 'a
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
Leo Famulari 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 wou
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.
Hello!
Leo Famulari skribis:
> On Tue, Sep 06, 2016 at 11:36:32PM +0200, Ludovic Courtès wrote:
>> Hi!
>>
>> l...@gnu.org (Ludovic Courtès) skribis:
>>
>> > I had an idea to use a ‘superseded’ entry in ‘properties’ that would
>> > tell ‘guix package’ et al. to upgrade to the new package:
>> >
On Tue, Sep 06, 2016 at 11:36:32PM +0200, Ludovic Courtès wrote:
> Hi!
>
> l...@gnu.org (Ludovic Courtès) skribis:
>
> > 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")
> >
Hi!
l...@gnu.org (Ludovic Courtès) skribis:
> 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
This is now implemented both a
12 matches
Mail list logo
