From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] create xfstests install target
Date: Fri, 02 Jan 2009 12:26:21 -0600 [thread overview]
Message-ID: <495E5C4D.80307@sandeen.net> (raw)
In-Reply-To: <20090102180247.GC29506@infradead.org>
Christoph Hellwig wrote:
> On Thu, Jan 01, 2009 at 04:25:18PM -0600, Eric Sandeen wrote:
>> Not sure what the best location for this is in the end, but that's
>> just a one-line change in builddefs.in if it should move. Currently
>> it goes to whatever configure thinks "libexecdir" is.
>
> I think that's incorrect. libexecdir is /usr/lib for FHS or /usr/libexec
> for BSDish filesystem layouts, but /use should be read-only mountable.
>
> Maybe /var/lib/xfstests as a start? That seems to be the dumping ground
> for random stuff that needs write access.
Ok, easy enough.
> Even better would be keeping
> the scripts under /usr/lib and the output in /var/lib, but that might
> be too much work.
Yeah at least right now I'm not that highly motivated. :)
>> +PKG_SBIN_DIR = @sbindir@
>
> This one doesn't actually seem to be used.
true, it's not ... I put it in there thinking about putting a wrapper in
sbin or /usr/sbin so tests could be launched from root's path ...
-Eric
> Otherwise looks good to me.
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-02 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 22:25 [PATCH] create xfstests install target Eric Sandeen
2009-01-02 3:47 ` [PATCH] xfstests Makepkgs framework, builds rpms Eric Sandeen
2009-01-02 18:03 ` Christoph Hellwig
2009-01-02 18:02 ` [PATCH] create xfstests install target Christoph Hellwig
2009-01-02 18:26 ` Eric Sandeen [this message]
2009-01-03 3:46 ` Eric Sandeen
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=495E5C4D.80307@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hch@infradead.org \
--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