From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
sandeen@sandeen.net, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/4] misc: support building flatpak images
Date: Wed, 8 Jan 2020 00:59:43 -0800 [thread overview]
Message-ID: <20200108085943.GC6971@infradead.org> (raw)
In-Reply-To: <20200107193537.GD917713@magnolia>
On Tue, Jan 07, 2020 at 11:35:37AM -0800, Darrick J. Wong wrote:
> In theory we could use it as a means to distribute uptodate xfs_repair
> so that anyone with a problem that their distro's copy of xfs_repair
> can't or won't fix can try upstream without having to build xfsprogs
> themselves.
And someone would allow a random weirdo package format access to their
disks?
> Also, can you elaborate on 'fucked up package delivery mechanism'?
It completely messes up how the system is supposed to work, and not your
are in a maze of unssuportable package versions just like npm.
next prev parent reply other threads:[~2020-01-08 8:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 1:22 [PATCH 0/4] xfsprogs: packaging cleanups Darrick J. Wong
2020-01-01 1:22 ` [PATCH 1/4] misc: support building flatpak images Darrick J. Wong
2020-01-07 14:20 ` Christoph Hellwig
2020-01-07 19:35 ` Darrick J. Wong
2020-01-08 8:59 ` Christoph Hellwig [this message]
2020-01-01 1:22 ` [PATCH 2/4] debian: turn debhelper compat level up to 11 Darrick J. Wong
2020-01-07 14:21 ` Christoph Hellwig
2020-01-07 18:51 ` Darrick J. Wong
2020-01-08 8:58 ` Christoph Hellwig
2020-01-01 1:23 ` [PATCH 3/4] debian: permit compat level 9 dh builds Darrick J. Wong
2020-01-01 1:23 ` [PATCH 4/4] xfs_scrub_all: failure reporting for the xfs_scrub_all job Darrick J. Wong
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=20200108085943.GC6971@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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.
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 NNTP newsgroup(s).