From: ludo@gnu.org (Ludovic Courtès)
To: bug-automake@gnu.org
Cc: guile-devel@gnu.org
Subject: Re: mtime of installed files
Date: Tue, 27 Jul 2010 10:18:39 +0200 [thread overview]
Message-ID: <87zkxdxrq8.fsf@gnu.org> (raw)
In-Reply-To: 20100721205359.GS4976@gmx.de
Hello!
Ralf Wildenhues <Ralf.Wildenhues@gmx.de> writes:
> Now I need to ask in more detail: do you actually need "newer" or just
> "not older"? Because if the latter, then you could just let the rule to
> install $(nodist_foobar_DATA) depend on the rule to install
> $(dist_foobar_SOURCES), the latter of which I assume you still need to
> write, and hook to install-data-local. Or you do something like
> mod_DATA = $(dist_foobar_SOURCES)
> ccache_DATA = $(nodist_foobar_DATA)
>
> The install rules then still have internal names
> (install-nodist_foobarDATA or install-ccacheDATA or so) but at least the
> right thing happens, as long as the same $(INSTALL_DATA) command is used
> in both cases.
>
> And if you need "newer" then you could "sleep 1" as last bit of your
> hand-written rule to install $(dist_foobar_SOURCES), or let the
> install-ccacheDATA depend on a guile-install-sleep helper rule which
> itself depends on the install-nodist_foobarDATA rule or so.
> However, that doesn't help you when "install -C" is used.
>
> Now, there's one more technical complication for adding the dependency:
> automake will not put out its own install-ccacheDATA rule if you use it
> as target anywhere (on the grounds that it's the only method to override
> an automake-provided target), which you don't want here; you can trick
> automake by assigning the name to some variable though:
> guile_install_ccacheDATA = install-ccacheDATA
> $(guile_install_ccacheDATA): install-modDATA
For the record, this was fixed along these lines. The auto-compile
mtime checks were also changed to checked for >= instead of ==:
http://git.savannah.gnu.org/cgit/guile.git/commit/?id=fefd60ba4ba751712c45c95362bbc2f858890678
Ralf: can you formally state that the rule names (‘install-ccacheDATA’,
etc.) are not going to change? :-)
Thank you!
Ludo’.
next prev parent reply other threads:[~2010-07-27 8:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 16:28 mtime of installed files Ludovic Courtès
2010-07-20 18:14 ` Ralf Wildenhues
2010-07-21 16:27 ` Ludovic Courtès
2010-07-21 20:53 ` Ralf Wildenhues
2010-07-27 8:18 ` Ludovic Courtès [this message]
2010-07-27 10:45 ` Ralf Wildenhues
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zkxdxrq8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-automake@gnu.org \
--cc=guile-devel@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).