Hi Nicolas,
On 10/18/07, Nicolas Martyanoff <[EMAIL PROTECTED]> wrote:
> The README tells I can use adsf-install. Fine !
>
> I run sbcl, and try a:
> (ASDF-INSTALL:INSTALL "usocket-0.3.5.tar.gz")
>
> Yep, but nope:
> debugger invoked on a SB-INT:SIMPLE-READER-PACKAGE-ERROR:
> SB-INT:SIMPLE-READER-PACKAGE-ERROR on #<SYNONYM-STREAM :SYMBOL
> SB-SYS:*STDIN* {90BB369}>: package "ASDF-INSTALL" not found
>
> I have asdf, but no asdf install, and there is no asdf-install on
> gentoo.
Sbcl should come with asdf-install, try (require 'asdf-install) to load it.
>
> As you see it, it's really painful. I know i'm a beginner in Lisp, and
> I think it shows how difficult it is to learn lisp, and for end-user,
> to use lisp applications.
Yes, the start of everything can be painful, but if you stick around
for a few more days, many things will quickly become much simpler.
> CONCLUSION (sorry for the long mail)
> Can't we get a simple package system (ala perl or python) ?
> A package should be installable with a simple make/make install, then
> it should be usable doing a simple (require "mypackage"), WITHOUT other
> work. No RC file to fill for each different lisp vm, no complicated
> system to manage packages.
>
> A CPAN-like repository would be perfect.
> Just imagine doing simply:
> clisp -x '(cpanlike:install apackage)'
>
> (With perl's CPAN: perl -MCPAN -e 'install My::Module')
As I just spend *several* days on getting some perl modules from CPAN
installed, I would say, that it wholly depends on the quality of the
package how easy it is to install. In general, asdf-install is as easy
to use as cpan. But if the compliation of the package does not work
out of the box, both systems can get equally hairy. Where
asdf/asdf-install really shines is in setting up the environment for
larger project, where you can recompile all files and dependencies
with a single asdf-operation.
And if I may add the plug: if you are looking for a simple and easy to
install solution for Lisp GUIs, have a look at LTk:
www.peter-herth.de/ltk
>
> There should be a simple way to launch an application.
> make -> compile the lisp files to binary.
> mylisp themainbinary
With sbcl it is dead-simple, once you have the application loaded, call
(save-lisp-and-die "filename" :toplevel #'mainfunction :executable t)
which will create the executable called "filename" which starts up
with calling "mainfunction" (replace the real name there...)
>
> So, I'll be very happy if you can enlight me on these problems, which
> totally spoils my discover of this language :(
>
Have patience :). Most of all, the world of Lisp is *different*, so it
takes a few days to get comfortable, but it is worth the effort.
Peter
_______________________________________________
Gardeners mailing list
[email protected]
http://www.lispniks.com/mailman/listinfo/gardeners
