Hi Ingvar,
While using ASDF-INSTALL to get a new noctool setup going, I found that the image package used strings instead of symbols for the packages that it depends on. This confuses the heck out of asdf-install (but seems to work OK for ASDF - HMMM... sounds like it might be a bug in ASDF-INSTALL, but... well, I don't want to spend the time reading the spec to determine that ;P :)
I've attached a modified version of image.asd from image-0.6 - the changes are by no means profound :)
Using the attached image.asd made my asdf-install go very smoothly. :)
hth, Jim
James E. Prewett Jim@Prewett.org download@hpc.unm.edu Systems Team Leader LoGS: http://www.hpc.unm.edu/~download/LoGS/ Designated Security Officer OpenPGP key: pub 1024D/31816D93 HPC Systems Engineer III UNM HPC 505.277.8210
Hi Ingvar,
While using ASDF-INSTALL to get a new noctool setup going, I found that the image package used strings instead of symbols for the packages that it depends on. This confuses the heck out of asdf-install (but seems to work OK for ASDF - HMMM... sounds like it might be a bug in ASDF-INSTALL, but... well, I don't want to spend the time reading the spec to determine that ;P :)
I've attached a modified version of image.asd from image-0.6 - the changes are by no means profound :)
Using the attached image.asd made my asdf-install go very smoothly. :)
If you look at noctool.asd, it too is using strings instead of symbols. I suspect it's more of an issue with ASDF-INSTALL than with the ASDF system definition, myself.
//Ingvar
I'm going to go ahead and change the strings in noctool.asd into symbols. When we do get something ready for the general public, I want the ASDF-INSTALL process to be as painless as possible :)
Jim
James E. Prewett Jim@Prewett.org download@hpc.unm.edu Systems Team Leader LoGS: http://www.hpc.unm.edu/~download/LoGS/ Designated Security Officer OpenPGP key: pub 1024D/31816D93 HPC Systems Engineer III UNM HPC 505.277.8210
On Thu, 12 Jun 2008, Ingvar wrote:
Hi Ingvar,
While using ASDF-INSTALL to get a new noctool setup going, I found that the image package used strings instead of symbols for the packages that it depends on. This confuses the heck out of asdf-install (but seems to work OK for ASDF - HMMM... sounds like it might be a bug in ASDF-INSTALL, but... well, I don't want to spend the time reading the spec to determine that ;P :)
I've attached a modified version of image.asd from image-0.6 - the changes are by no means profound :)
Using the attached image.asd made my asdf-install go very smoothly. :)
If you look at noctool.asd, it too is using strings instead of symbols. I suspect it's more of an issue with ASDF-INSTALL than with the ASDF system definition, myself.
//Ingvar
noctool-devel mailing list noctool-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/noctool-devel
Jim writes:
I'm going to go ahead and change the strings in noctool.asd into symbols. When we do get something ready for the general public, I want the ASDF-INSTALL process to be as painless as possible :)
Hm, my own "mucks with ASDF systems" code doesn't seem to be having any problems. :(
But, looking at (for example) Skippy, it seems as it is indeed using symbols rather than strings. I've always used strings, myself, since I believe taht's how Dan Barlow did it, back in the days.
Go ahead and clean it up!
//Ingvar
-
Ingvar -
Jim Prewett