From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Allan Webber Subject: Re: Fixing non-reproducibility in some guile packages Date: Mon, 13 Feb 2017 10:25:56 -0600 Message-ID: <8760ke5a7f.fsf@dustycloud.org> References: <87fujly0pu.fsf@dustycloud.org> <87bmu8y7sx.fsf@dustycloud.org> <87tw80pgpl.fsf@gnu.org> <87efz35ncm.fsf@dustycloud.org> <87h93y4nr3.fsf@gmail.com> <87efz2ef6x.fsf@igalia.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-reply-to: <87efz2ef6x.fsf@igalia.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Sender: "guile-devel" To: Andy Wingo Cc: guix-devel@gnu.org, guile-devel@gnu.org, Maxim Cournoyer List-Id: guix-devel.gnu.org 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? :)