From: Leo Famulari <leo@famulari.name>
To: tobias.geerinckx.rice@gmail.com
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/2] gnu: Add btrfs-progs.
Date: Thu, 11 Feb 2016 21:43:19 -0500 [thread overview]
Message-ID: <20160212024319.GC25360@jasmine> (raw)
In-Reply-To: <1455076907-20572-2-git-send-email-tobias.geerinckx.rice@gmail.com>
On Wed, Feb 10, 2016 at 05:01:46AM +0100, tobias.geerinckx.rice@gmail.com wrote:
> From: Tobias Geerinckx-Rice <tobias.geerinckx.rice@gmail.com>
>
> * gnu/packages/linux.scm (btrfs-progs): New variable.
[...]
> + (arguments
> + '(#:tests? #f)) ;no test suite
I altered this to run `make test` and disabled parallel tests because
they failed repeatedly on 002-uuid-rewrite.
> + (inputs `(("e2fsprogs" ,e2fsprogs)
> + ("libblkid" ,util-linux)
> + ("libuuid" ,util-linux)
> + ("zlib" ,zlib)
> + ("lzo" ,lzo)))
> + (native-inputs `(("pkg-config" ,pkg-config)
> + ("asciidoc" ,asciidoc)
> + ("xmlto" ,xmlto)
> + ("libxml2" ,libxml2) ;for building documentation
> + ("docbook-xml" ,docbook-xml)
> + ("docbook-xsl" ,docbook-xsl)))
> + (home-page "https://btrfs.wiki.kernel.org/")
> + (synopsis "Create and manage btrfs copy-on-write file systems")
> + (description "Btrfs is a copy-on-write (CoW) filesystem for Linux aimed at
> +implementing advanced features while focusing on fault tolerance, repair and
> +easy administration.")
> + (license license:gpl2+)))
> --
> 2.6.3
>
>
next prev parent reply other threads:[~2016-02-12 2:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 4:01 Adding btrfs-progs tobias.geerinckx.rice
2016-02-10 4:01 ` [PATCH 1/2] gnu: Add btrfs-progs tobias.geerinckx.rice
2016-02-12 2:43 ` Leo Famulari [this message]
2016-02-10 4:01 ` [PATCH 2/2] install: Add btrfs-progs to the image tobias.geerinckx.rice
2016-02-12 2:44 ` Leo Famulari
2016-02-12 9:07 ` Ludovic Courtès
2016-02-12 21:47 ` Leo Famulari
2016-02-12 2:41 ` Adding btrfs-progs Leo Famulari
2016-02-12 16:03 ` Tobias Geerinckx-Rice
2016-02-12 22:10 ` 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=20160212024319.GC25360@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=tobias.geerinckx.rice@gmail.com \
/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.