Re: asdf-install for cmucl?

Raymond Toy <[email protected]> writes:

> Note that this would be a contrib, not an "official" part of CMUCL.
> Ideally, this would be maintained elsewhere, but the cclan version
> seems to have languished and is very different from the SBCL version,
> which seems to be the canonical one.  I think it would be unlikely for
> SBCL to keep it up-to-date with CMUCL. :-)

The cclan version is a direct (though distant) ancestor of the one in
SBCL: nothing has been done to it since I put it in SBCL.

If someone wanted to become 'cmucl maintainer', for want of a better
word, for asdf-install, I'd be happy to resuscitate the cclan version
so that they could get cvs hacking privileges from the cclan admins.
(This offer also avilable to hackers of other implementations: openmcl
or clisp or whoever).  In SBCL we already sync asdf itself directly
with the cclan version, so it wouldn't hurt to do similarly for
asdf-install.

Some factoring of the unportable bits in asdf-install would probably
be a win.  A brief scan says we should be concerned about (a) getting
a network connection, (b) stream encodings (we cheat with line
endings, and we expect to be able to send arbitrary binary data over a
character stream), and (c) a raft of good-for-sbcl assumptions about
pathnames and similar.  None of which are unfixable (and (b) isn't an
issue for CMUCL anyway), but it'd be good to expose them.


-dan

-- 

 http://web.metacircles.com/ - Open Source software development and support

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQA/4Ti6HDK5ZnWQiRMRAvc3AJ4/KUAe1t90E+//4v1PDsASPCc+7ACfRU83
T2Z6Vr2T28nUXLQCGBxbHeA=
=9bNM
-----END PGP SIGNATURE-----