diogo...@gmail.com (Diogo F. S. Ramos) writes: > "Desmond O. Chang" <doch...@gmail.com> writes: > >> In conclusion, if you're creating a new CL package, no need to >> Build-Depend on dh-lisp. >> >> >> The CLID on alioth is really outdated. Do not learn it at this >> moment. We should rewrite it. > > Thank you for the clarification. > > Now, what are the directions an application needs to follow to package a > Lisp application? > > Should it still install its files inside > `/usr/share/common-lisp/source/package' or should it install them at > `/usr/share/package'? > > Also, what about the .asd file? Should it install one .conf file inside > `/etc/common-lisp/source-registry.conf.d' that points to the path of > the .asd file so ASDF can find it? > > What I'm thinking is an application, not a library, which can be run > from a REPL or from a startup script installed at `/usr/bin'.
You should install all the lisp files in /usr/share/common-lisp/source/<package>. No need to configure .asd file, ASDF2 will find all asd files in the directory above. Other files should be installed according to FHS & Debian Policy. The script in /usr/bin/ simply run a CL implementation, e.g. SBCL, and SBCL will find .asd file using ASDF2. Thanks, Des _______________________________________________ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-common-lisp-devel
