xach at xach.com
Tue Dec 18 16:24:52 UTC 2012
Faré <fahree at gmail.com> writes:
> On Tue, Dec 18, 2012 at 11:09 AM, Zach Beane <xach at xach.com> wrote:
>> Faré <fahree at gmail.com> writes:
>>> I don't know what to say, except: "if you've been installing SBCL from
>>> updated source, you might have to recompile some contrib".
>> I'd prefer something less disruptive, please.
> You want me to special case the detection that SBCL contribs built
> from an updated source may be out of date?
> That's not going to be very clean. How many people build from updated
> source, and if they do how hard is it
> for them to rebuild from source and/or get write permissions to let
> ASDF update sb-md5.fasl in its installed location?
> Is that kluge worth it? I'm not even sure how to do it. Do you have a
> better solution?
The only solution I understand so far is to run SBCL as root and rebuild
the contribs, or modify the system directory permissions so a user can
rebuild the contribs. That seems like a hassle, and I'd prefer not to do
it, especially since I have a lot of SBCL installations around. It's
also unlike anything else I normally do to fix CL problems.
Are there changes to SBCL that could be made to mitigate the problem?
"Update SBCL and reinstall" is something I'm quite familiar with doing.
More information about the asdf-devel