From: Dave Chinner <david@fromorbit.com>
To: dsterba@suse.cz, xfs@oss.sgi.com
Subject: Re: [PATCH 2/5] xfstests: use value of FSTYP if defined externally
Date: Tue, 21 Jan 2014 09:22:54 +1100 [thread overview]
Message-ID: <20140120222254.GK18112@dastard> (raw)
In-Reply-To: <20140120181901.GZ6498@suse.cz>
On Mon, Jan 20, 2014 at 07:19:01PM +0100, David Sterba wrote:
> On Mon, Jan 20, 2014 at 01:13:45PM +1100, Dave Chinner wrote:
> > On Thu, Jan 16, 2014 at 06:07:12PM +0100, David Sterba wrote:
> > > --- a/check
> > > +++ b/check
> > > @@ -33,7 +33,7 @@ showme=false
> > > have_test_arg=false
> > > randomize=false
> > > here=`pwd`
> > > -FSTYP=xfs
> > > +FSTYP=${FSTYP:-xfs}
> >
> > ":-xfs" means assign the value of $xfs if $FTYPE is null. xfs is not
> > a variable....
>
> Docs say that
>
> ${parameter:-word}
> If parameter is unset or null, the expansion of word is substituted.
> Otherwise, the value of parameter is substituted.
>
> so 'xfs' will expand to itself. And I did test this one with:
>
> $ cat default.sh << EOF
> FSTYP=${FSTYP:-xfs}
> echo $FSTYP
> EOF
>
> $ cat external.sh << EOF
> FSTYP=btrfs
> source default.sh
> EOF
>
> $ sh default.sh
> xfs
>
> $ sh external.sh
> btrfs
Funny, I did the same tests to check and kept getting no output
instead of the "xfs" result. Changing it to := made it work just
fine. Oh well... :/
> > > -# Autodetect fs type based on what's on $TEST_DEV
> > > -if [ "$HOSTOS" == "Linux" ]; then
> > > +# Autodetect fs type based on what's on $TEST_DEV unless it's been set
> > > +# externally
> > > +if [ -z "$FSTYP" -a "$HOSTOS" == "Linux" ]; then
> >
> > If the default value expansion is fixed, FSTYP will always have a
> > value here Hence it will never, ever probe.
>
> > > FSTYP=`blkid -c /dev/null -s TYPE -o value $TEST_DEV`
> > > fi
> > > export FSTYP
> >
> > I suspect what you want is:
> >
> > -FSTYP=xfs
> >
> > .....
> >
> > if [ -z "$FSTYP" -a "$HOSTOS" == "Linux" ]; then
> > FSTYP=`blkid -c /dev/null -s TYPE -o value $TEST_DEV`
> > fi
> > FSTYP=${FSTYP:=xfs}
> > export FSTYP
>
> Right, the default assignment has to be last. I'll use the := form
> to be consistent with what's used in the file, though :- works here as
> well, just does not assign the variable within the ${...} expression.
> The result is the same.
Thanks.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-01-20 22:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 17:07 [PATCH 0/5] xfstests: A few updates to non-test code David Sterba
2014-01-16 17:07 ` [PATCH 1/5] xfstests: fix minor build warning David Sterba
2014-01-16 22:11 ` Ben Myers
2014-01-16 17:07 ` [PATCH 2/5] xfstests: use value of FSTYP if defined externally David Sterba
2014-01-20 2:13 ` Dave Chinner
2014-01-20 18:19 ` David Sterba
2014-01-20 22:22 ` Dave Chinner [this message]
2014-01-16 17:07 ` [PATCH 3/5] xfstests: don't suggest to run full diff when DIFF_LENGTH is 0 David Sterba
2014-01-20 2:25 ` Dave Chinner
2014-01-16 17:07 ` [PATCH 4/5] xfstests: accept tests/ prefix for test name on commandline David Sterba
2014-01-16 17:07 ` [PATCH 5/5] xfstests: update lsqa.pl for new tests layout David Sterba
2014-01-20 5:46 ` [PATCH 0/5] xfstests: A few updates to non-test code Dave Chinner
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=20140120222254.GK18112@dastard \
--to=david@fromorbit.com \
--cc=dsterba@suse.cz \
--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