From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: tytso@mit.edu, ext4 development <linux-ext4@vger.kernel.org>,
xfs-oss <xfs@oss.sgi.com>, Giel de Nijs <giel@vectorwise.com>
Subject: Re: [PATCH] xfstests 224: test aio hole-fill at 4g
Date: Sat, 30 Jan 2010 13:46:10 -0600 [thread overview]
Message-ID: <4B648C82.3040801@sandeen.net> (raw)
In-Reply-To: <20100130191113.GC10181@infradead.org>
Christoph Hellwig wrote:
> On Sat, Jan 30, 2010 at 12:31:26PM -0600, Eric Sandeen wrote:
>> These are the deps that I know xfstests has, to build and to run:
>>
>> BuildRequires: autoconf, libtool, xfsprogs-devel, e2fsprogs-devel
>> BuildRequires: libacl-devel, libattr-devel, libaio-devel
>>
>> Requires: bash, xfsprogs, xfsdump, perl, acl, attr, bind-utils
>> Requires: bc, indent, quota
>>
>> which isn't so bad...
>
> Doesn't seem to bad. Indent is afaik only needed for the weird 122 test
> which doesn't apply to non-xfs filesystems.
and FWIW, we do:
_require_command /usr/bin/indent
so it'll just not run if it's not there (the above was for an rpm
attempt I made, wishing to automatically pull in everything that
might possibly be needed.)
-Eric
>> I'm not sure an xfsprogs dependency is so onerous; plenty has depended
>> on e2fsprogs through the years and we've lived with that ;) But
>> the lag time for xfsprogs to use released xfs_io functionality is a
>> bit of a bummer.
>>
>> But I guess I don't have a great answer for who else uses xfs_io:
>
> I use xfs_io in lots various local scripts. It's a really handly
> tool for exercising some of the more weird I/O related syscalls.
>
prev parent reply other threads:[~2010-01-30 19:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 20:05 [PATCH] xfstests 224: test aio hole-fill at 4g Eric Sandeen
2010-01-30 10:55 ` Christoph Hellwig
2010-01-30 16:15 ` Eric Sandeen
2010-01-30 17:25 ` tytso
2010-01-30 18:31 ` Eric Sandeen
2010-01-30 19:11 ` Christoph Hellwig
2010-01-30 19:46 ` Eric Sandeen [this message]
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=4B648C82.3040801@sandeen.net \
--to=sandeen@sandeen.net \
--cc=giel@vectorwise.com \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=xfs@oss.sgi.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.
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).