unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
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 21:19:24 +0200	[thread overview]
Message-ID: <m3vd8aufk3.fsf@unquote.localdomain> (raw)
In-Reply-To: <87lj96uo5x.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 20 Jul 2010 18:13:30 +0200")

On Tue 20 Jul 2010 18:13, ludo@gnu.org (Ludovic Courtès) writes:

> Hello,
>
> Andy Wingo <wingo@pobox.com> writes:
>
>> 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.)

Yes, that is what I mean.

>> AFAIR [“make install” does not preserve mtimes] on my system -- I
>> wouldn't have added the install-hook in Guile otherwise...
>
> Oh, OK.  I’ll mail bug-automake then.

I saw your mail, and it was good; but I was actually thinking that we
should have native Guile support. Automake has native support for lots
of languages, but not Guile. Not yet :)

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2010-07-20 19:19 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
2010-07-20 16:13           ` Ludovic Courtès
2010-07-20 19:19             ` Andy Wingo [this message]
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=m3vd8aufk3.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).