From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: mtime of fresh .go
Date: Tue, 20 Jul 2010 09:46:04 +0200 [thread overview]
Message-ID: <m3pqyiwq83.fsf@unquote.localdomain> (raw)
In-Reply-To: <87wrsrxgkb.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 20 Jul 2010 00:17:08 +0200")
Hi,
On Tue 20 Jul 2010 00:17, ludo@gnu.org (Ludovic Courtès) writes:
> Andy Wingo <wingo@pobox.com> writes:
>
>> * RPM or Deb systems typically timestamp their files based on the times
>> they were built, not installed, and we don't have guarantees that
>> upgrading a package won't actually move the mtime into the past.
>
> What matters is that the mtime(.go) >= mtime(.scm), and I’d expect it to
> be preserved by packaging systems, even after an upgrade, no?
Not all packages with Scheme files will have .go files, so you get
compilation by the user in some cases. But even if the version
increases, you are not guaranteed that the mtime increases. This is
besides the issue of downgrades, of course.
>> * When installing source code (via _SOURCES / _DATA), you don't have
>> any guarantees about the relations between the times of the SOURCE
>> and DATA files, *as installed*.
>
> Apparently “make install” preserves mtimes on my system. IOW, since
> uninstalled .gos have mtime >= uninstalled .scms, the same holds for
> installed .gos and .scms.
AFAIR it does not on mine -- I wouldn't have added the install-hook in
Guile otherwise...
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-07-20 7:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 8:07 mtime of fresh .go Ludovic Courtès
2010-07-18 13:03 ` Andy Wingo
2010-07-18 22:31 ` Ludovic Courtès
2010-07-19 19:10 ` Andy Wingo
2010-07-19 22:17 ` Ludovic Courtès
2010-07-20 7:46 ` Andy Wingo [this message]
2010-07-20 16:13 ` Ludovic Courtès
2010-07-20 19:19 ` Andy Wingo
2010-07-21 15:57 ` Ludovic Courtès
2010-07-20 7:46 ` Andy Wingo
2010-07-20 16:30 ` Ludovic Courtès
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=m3pqyiwq83.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).