From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Andy Wingo <wingo@igalia.com>
Cc: guix-devel@gnu.org, guile-devel@gnu.org,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: Re: Fixing non-reproducibility in some guile packages
Date: Mon, 13 Feb 2017 10:25:56 -0600 [thread overview]
Message-ID: <8760ke5a7f.fsf@dustycloud.org> (raw)
In-Reply-To: <87efz2ef6x.fsf@igalia.com>
Andy Wingo writes:
> In some future (is it near or far?), the source -> compiled function
> needs additional inputs: checksums or timestamps of "build inputs" or
> so, so that when for-syntax definitions (like macros) change, users of
> those definitions will recompile. That is a harder problem though.
Ah yeah, I've been bit by this before. Though, I imagine we'd run into
a problem where we'd never know how to "garbage collect" anything in
~/.cache/guile/ . "Maybe not a problem", except if you're hacking some files
constantly... :)
Maybe every guile hacker needs to get in the habit of
`rm -rf ~/.cache/guile/' though? :)
next prev parent reply other threads:[~2017-02-13 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87fujly0pu.fsf@dustycloud.org>
[not found] ` <87bmu8y7sx.fsf@dustycloud.org>
[not found] ` <87tw80pgpl.fsf@gnu.org>
[not found] ` <87efz35ncm.fsf@dustycloud.org>
[not found] ` <87h93y4nr3.fsf@gmail.com>
2017-02-13 7:13 ` Fixing non-reproducibility in some guile packages Andy Wingo
2017-02-13 16:25 ` Christopher Allan Webber [this message]
2017-02-13 17:39 ` Maxim Cournoyer
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=8760ke5a7f.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=guile-devel@gnu.org \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=wingo@igalia.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 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).