All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Jan Tulak <jtulak@redhat.com>
Cc: fstests@vger.kernel.org, eguan@redhat.com
Subject: Re: [PATCH v3] xfstests: Fix installation for extended
Date: Fri, 1 Jul 2016 11:16:42 +1000	[thread overview]
Message-ID: <20160701011642.GV27480@dastard> (raw)
In-Reply-To: <1467302784-32755-1-git-send-email-jtulak@redhat.com>

On Thu, Jun 30, 2016 at 06:06:24PM +0200, Jan Tulak wrote:
> xfstests supports extended test names like 314-foo-bar, but installation of
> these tests was skipped (not matching a regexp). So this patch fixes the
> makefiles in tests/xfs/.
> 
> This change will have to be repeated later for other directories, as adding it
> now everywhere would cause make install to fail if no such extended name is
> present in the dir.
> 
> Signed-off-by: Jan Tulak <jtulak@redhat.com>
> ---
> UPDATE:
> Let it be just in tests/xfs/.
> 
> NOTE: if tested without at first merging my 400-input-valiation test, make
> install will fail again. :-)

This really should be done in a way that doesn't fail like this so
it can simply be added to all the tests/<fs>/Makefile and then we
can ignore the problem again.

The usual way of doing this from with the makefile is to use
wildcard rules, something like:

INSTALL_FILES = $(wildcard <regex>)

install: $(addsuffix -install,$(INSTALL_FILES))
	[.....]

%-install:
	$(INSTALL) -m 664 $* $(TARGET_DIR)


You can use multiple wildcard matches for INSTALL_FILES if you can't
write a single regex to grab all the filesystem that need
installing.

See, for example, tests/Makefile for an example of exactly this sort
of wildcard matching so that the makefile does not need updating
every time we add a new tests subdirectory.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  parent reply	other threads:[~2016-07-01  1:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 14:57 [PATCH] xfstests: Fix installation for extended names Jan Tulak
2016-06-30  3:38 ` Eryu Guan
2016-06-30  8:32   ` Jan Tulak
2016-06-30  8:35 ` [PATCH v2] " Jan Tulak
2016-06-30 13:33   ` Eryu Guan
2016-06-30 15:19     ` Jan Tulak
2016-06-30 15:35       ` Eryu Guan
2016-06-30 16:06 ` [PATCH v3] xfstests: Fix installation for extended Jan Tulak
2016-06-30 16:08   ` Jan Tulak
2016-06-30 16:21     ` Eryu Guan
2016-07-01  1:16   ` Dave Chinner [this message]
2016-07-01 15:51     ` Jan Tulak

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=20160701011642.GV27480@dastard \
    --to=david@fromorbit.com \
    --cc=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=jtulak@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.