From: Leo Famulari <leo@famulari.name>
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 5/6] gnu: Add borg.
Date: Tue, 22 Mar 2016 17:25:25 -0400 [thread overview]
Message-ID: <20160322212525.GB13372@jasmine> (raw)
In-Reply-To: <87mvpqtgbu.fsf@gmail.com>
On Tue, Mar 22, 2016 at 11:20:37PM +0300, Alex Kost wrote:
> Leo Famulari (2016-03-22 01:52 +0300) wrote:
>
> > On Mon, Mar 21, 2016 at 06:35:19PM -0400, Leo Famulari wrote:
> >> I asked upstream about some warnings during the docs generation, and
> >> they pointed out that I needed to add a command line. I've attached a
> >> revised patch.
> >>
> >> Can I get some feedback on it?
> >
> > Based on feedback on #guix, I've revised it again. Attached...
>
> > From: Leo Famulari <leo@famulari.name>
> > Date: Mon, 14 Mar 2016 19:34:25 -0400
> > Subject: [PATCH 5/6] gnu: Add borg.
> >
> > * gnu/packages/backup.scm (borg): New variable.
>
> [...]
> > +(define-public borg
> > + (package
> > + (name "borg")
> > + (version "1.0.0")
> > + (source (origin
> > + (method url-fetch)
> > + (uri (pypi-uri "borgbackup" version))
> > + (sha256
> > + (base32
> > + "0wa6cvqs3rni5nwrgagigchcly8a53rxk56z0zn8iaii2cqrw2sh"))))
> > + (build-system python-build-system)
> > + (arguments
> > + `(#:phases
> > + (modify-phases %standard-phases
> > + (add-after 'unpack 'set-env
> > + (lambda* (#:key inputs #:allow-other-keys)
> > + (let ((openssl (assoc-ref inputs "openssl"))
> > + (lz4 (assoc-ref inputs "lz4")))
> > + (setenv "BORG_OPENSSL_PREFIX" openssl)
> > + (setenv "BORG_LZ4_PREFIX" lz4)
> > + (setenv "PYTHON_EGG_CACHE" "/tmp")
> > + #t)))
>
> If you keep #t inside 'let', then align it to (setenv ...), or move it
> away from 'let':
>
> (lambda* (#:key inputs #:allow-other-keys)
> (let ((openssl (assoc-ref inputs "openssl"))
> (lz4 (assoc-ref inputs "lz4")))
> (setenv "BORG_OPENSSL_PREFIX" openssl)
> (setenv "BORG_LZ4_PREFIX" lz4)
> (setenv "PYTHON_EGG_CACHE" "/tmp"))
> #t)
>
> Note the difference: another ')' after the last (setenv ...).
>
> > + (add-after 'install 'docs
>
> Perhaps it is better to call this phase 'install-doc'. It's a usual
> name that can be met in other recipes. There is also
> 'install-man-pages' phase name, but I prefer 'install-doc'.
Sure, I'll take your advice!
>
> The rest looks good to me, so if you checked that this program works, I
> think you can push this patchset.
I've been using this program for a few months without problems (yes, I
do restore from time to time).
It's being developed very rapidly for something so critical as a backup
program, so I think that it's still a bit experimental. I could allude
to that in the description. What do you think?
next prev parent reply other threads:[~2016-03-22 21:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 23:34 [PATCH 0/6] Add borg Leo Famulari
2016-03-14 23:34 ` [PATCH 1/6] gnu: python-msgpack: Update to 0.4.7 Leo Famulari
2016-03-14 23:34 ` [PATCH 2/6] gnu: python-msgpack: Use 'python2-variant' Leo Famulari
2016-03-14 23:34 ` [PATCH 3/6] gnu: attic: Specify dependency on python-llfuse@0.41 Leo Famulari
2016-03-15 8:58 ` Alex Kost
2016-03-15 9:13 ` Leo Famulari
2016-03-14 23:34 ` [PATCH 4/6] gnu: python-llfuse: Update to 1.0, keep 0.41 variant Leo Famulari
2016-03-15 8:53 ` Alex Kost
2016-03-15 9:13 ` Leo Famulari
2016-03-15 10:12 ` Mathieu Lirzin
2016-03-15 16:25 ` Ludovic Courtès
2016-03-21 2:49 ` Leo Famulari
2016-03-21 8:52 ` Alex Kost
2016-03-14 23:34 ` [PATCH 5/6] gnu: Add borg Leo Famulari
2016-03-15 9:11 ` Alex Kost
2016-03-15 9:18 ` Leo Famulari
2016-03-21 21:31 ` Leo Famulari
2016-03-21 22:35 ` Leo Famulari
2016-03-21 22:52 ` Leo Famulari
2016-03-22 20:20 ` Alex Kost
2016-03-22 21:25 ` Leo Famulari [this message]
2016-03-23 8:14 ` Alex Kost
2016-03-23 20:49 ` Efraim Flashner
2016-03-14 23:34 ` [PATCH 6/6] gnu: python-llfuse@0.41: Update to 0.41.1 Leo Famulari
2016-03-24 21:55 ` [PATCH 0/6] Add borg 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160322212525.GB13372@jasmine \
--to=leo@famulari.name \
--cc=alezost@gmail.com \
--cc=guix-devel@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).