unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Brice Waegeneire <brice@waegenei.re>
To: Leo Famulari <leo@famulari.name>
Cc: 39332@debbugs.gnu.org,
	Jonathan Brielmaier <jonathan.brielmaier@web.de>,
	Guix-patches
	<guix-patches-bounces+brice+lists=waegenei.re@gnu.org>
Subject: [bug#39332] [PATCH] system: Add btrfs-progs to %BASE-PACKAGES.
Date: Wed, 29 Jan 2020 11:19:18 +0000	[thread overview]
Message-ID: <bb3bdaeccbfbb11aecd6a5ce124c9b7e@waegenei.re> (raw)
In-Reply-To: <20200128231445.GA17331@jasmine.lan>

On 2020-01-28 23:14, Leo Famulari wrote:
> On Tue, Jan 28, 2020 at 11:42:16PM +0100, Jonathan Brielmaier wrote:
>> This adds btrfs-progs, zstd and lzo to the closure with a total of
>> 7.7MiB. So that doesn't seem to big. I'm just wondering if we need 
>> btrfs
>> support here at all, as I would call btrfs still kind of exotic apart
>> from *SUSE distros and Facebook's backend.
> 
> Yeah, maybe it is too niche. I use it on all my machines but that's 
> just
> me. Let's wait to see if there are more comments before deciding.

Maybe %base-packages is the wrong place to add it. But it should at 
least be added to the system profile if a file-systems entry uses btrfs 
which isn't the case as I recall.

  reply	other threads:[~2020-01-29 11:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28 22:26 [bug#39332] [PATCH] system: Add btrfs-progs to %BASE-PACKAGES Leo Famulari
2020-01-28 22:42 ` Jonathan Brielmaier
2020-01-28 23:14   ` Leo Famulari
2020-01-29 11:19     ` Brice Waegeneire [this message]
2020-02-08  0:21       ` bug#39332: " 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=bb3bdaeccbfbb11aecd6a5ce124c9b7e@waegenei.re \
    --to=brice@waegenei.re \
    --cc=39332@debbugs.gnu.org \
    --cc=guix-patches-bounces+brice+lists=waegenei.re@gnu.org \
    --cc=jonathan.brielmaier@web.de \
    --cc=leo@famulari.name \
    /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).