[asdf-devel] ASDF:OOS LOAD-OP :FORCE T and SBCL contribs
gwking at metabang.com
Fri May 15 19:02:09 UTC 2009
Just FYI that I've been swamped yesterday and today but will turn my
fragmented mind back towards this over the weekend (whether you cheer
or shudder at the prospect is up to you <smile>).
On May 13, 2009, at 12:17 PM, Nikodemus Siivola wrote:
> 2009/5/13 Robert Goldman <rpgoldman at sift.info>:
>> I guess that this is a matter of aesthetics, about which we'll have
>> agree to disagree. I think small snippets of code that are located
>> close to the things that they are supposed to configure are easier to
>> track, understand, and even test than stuff that's squirreled away
>> non-locally (e.g., in /usr/local/etc/sbclrc).
> To a degree, yes. However, "X doesn't work on my system" is made a lot
> harder to reproduce / debug remotely the more sources of code there
> are. Also, ASFD just deprecated preference files some time back -- and
> I'm not sure how configuration files would differ from preference
>> I think there are a a couple of facts about what I'm doing, and how
>> differs from what you are doing that may make for this difference of
>> I'm concerned with delivering applications, rather than delivering a
>> lisp implementation, which seems more like your concern.
>> This means that I'm typically not messing with a site's global lisp
>> configuration, but rather local configurations.
> I would have imagined that most lisp applications would be delivered
> independently of the lisp development framework possibly at place.
> (Which in my books includes all the .lisp, .asd and .fasl files: the
> application either delivers all it's own ancilliary files or is a
> single executable.) Maybe this is not so.
> Can you describe your typical delivery scenario?
>> I'm also often working with multiple lisp implementations
>> which also leads me to see this as an issue of configuring the
>> individual libraries.
>> For that matter, I'm typically working with > 1 different lisp
>> in different lisp configurations (the projects have different source
>> repositories, assume different libraries, etc.). So I typically work
>> with multiple different asdf:*central-registry* configurations.
> This is something I have almost no experience in. Can you outline the
> major issues as you see them?
> -- Nikodemus
> asdf-devel mailing list
> asdf-devel at common-lisp.net
Gary Warren King, metabang.com
Cell: (413) 559 8738
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM * gwking on twitter
More information about the asdf-devel