From gwking at metabang.com Sun Mar 1 00:20:46 2009 From: gwking at metabang.com (Gary King) Date: Sat, 28 Feb 2009 19:20:46 -0500 Subject: [asdf-install-devel] unable to find installed package In-Reply-To: <408995400902241734y4421c7a5q7e2268f39d476578@mail.gmail.com> References: <408995400902241734y4421c7a5q7e2268f39d476578@mail.gmail.com> Message-ID: Hi Hugh, You're right that the installer should take care of this. This is the variable that ASDF-Install uses to figure out how to do this: (defvar *system-file-installer* 'maybe-symlink-sysfile "A funcallable object that will install a system file so that it can be found by its defsystem. This function is not defsystem-specific. It will receive two arguments; a pathname designating a directory where the system file should be registered, and a pathname designating a system file to be registered. The return value is ignored. The default value is a function that creates a symbolic link on UNIX-like systems, and does nothing on Windows.") As you can see, it doesn't do anything on windows. There are certainly ways that this could be improved but it's not clear when the time will be produced to do so. Sorry. On Feb 24, 2009, at 8:34 PM, Hugh Myers wrote: > I'm running asdf-install with CLisp and Cygwin. Pretty much a happy > camper except for one niggle. After installing a package, say cl- > ppcre I am unable to execute a (asdf:operate 'asdf:load-op :cl- > ppcre) until I add a sym-link from the 'registry' directory to the > (in my case) /usr/local/asdf-install/site-systems/cl-ppcre.asd file > (I suppose the link is from the file to the directory, but you know > what I mean). After that it works fine. Seems like this is something > the install procedure should do? I notice though that even with the > sym-link, placing such a command in .clisprc doesn't do anything, > seemingly ignored. I know more ways to screw up a simple set of > instructions than most would believe possible so I'm assuming that > I've taken a wrong turn somewhere along the way. Guidance from > anyone would be most helpful... > > --hsm > _______________________________________________ > asdf-install-devel mailing list > asdf-install-devel at common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-install-devel -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter From Juliusz.Chroboczek at pps.jussieu.fr Sun Mar 15 12:01:00 2009 From: Juliusz.Chroboczek at pps.jussieu.fr (Juliusz Chroboczek) Date: Sun, 15 Mar 2009 12:01:00 -0000 Subject: [asdf-install-devel] ASDF-install and CL-Yacc: wrong system name Message-ID: <7iiqmbnjmn.fsf@lanthane.pps.jussieu.fr> Hi, I'm the author of CL-Yacc, which is ASDF-installable. Or at least used to be. CL-Yacc lives in a tarball called cl-yacc-0.3.tar.gz. It also lives in a Debian package called cl-yacc. Since the ``cl-'' prefix makes no sense in a system name, the system it defines is called ``yacc'' and lives in a file called ``yacc.asd''. This is fine for Debian's Common Lisp stuff. OTOH, recent versions of ASDF-Install complain that they cannot find the ``cl-yacc'' system. I'm not going to rename the system, since that would break my users' code, and I'm not going to include two systems, as that would cause useless confusion. I can see two solutions: 1. ASDF-Install could strip the ``cl-'' prefix when searching for a system; 2. there could be a way for the package author (me) to specify the actual system name in a metadata file. Either would be fine with me, as long as people stop e-mailing me with the problem. Juliusz