[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: mtime of fresh .go
From: |
Ludovic Courtès |
Subject: |
Re: mtime of fresh .go |
Date: |
Tue, 20 Jul 2010 18:13:30 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) |
Hello,
Andy Wingo <address@hidden> writes:
> On Tue 20 Jul 2010 00:17, address@hidden (Ludovic Courtès) writes:
>
>> Andy Wingo <address@hidden> 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.
Do you mean that installing a new version of a Guile-using package that
does not ship .go files may not trigger a recompilation? (Whereas you
would want automatic recompilation.)
>>> * 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...
Oh, OK. I’ll mail bug-automake then.
Thanks,
Ludo’.