Hi Peter, On Fri, Dec 3, 2010 at 14:01, Peter Van Eynde <pvane...@mailworks.org> wrote: > Hello Desmond, > > On 01/12/10 03:10, Desmond O. Chang wrote: >> >> ASDF2 has been mature. C-L-C is basically a thin wrapper now. I plan >> to remove some redundant features from c-l-c and related packages. > > This is a good idea and a path that I would have followed if RL was not > preventing me from contributing at the moment.
I always welcome your contribution. > >> - Remove clc-(un)register-user-package. >> - Remove (un)register-common-lisp-implementation. > > Don't forget the 'Breaks' that you will have to issue against all previous > CL packages, as removing these scripts will in fact break them. > > Migration to this new system can be tricky... Thanks for reminding me. That's important. > >> * About clbuild >> >> Personally I don't like clbuild. I think a library installer such as >> clbuild should work in user space, you can put its code in a directory >> like ~/bin. So clbuild will be removed. > > There is a use-case for a 'global' clbuild: if you are the admin of for > example a student server and you want to offer a stable library of CL > packages for users... > > We should retain some way for the admin to install CL libraries in a global > manner. But there is no 'standard' way in the CL world. Clbuild is just one of them. As I said, they can be uploaded as new packages. Here is my opinion: - /usr/share/common-lisp/... for APT - /usr/local/share/common-lisp/... for admin - /var/lib/... for 3rd party managers installed by system - $HOME/... for 3rd party managers installed by user Thanks, Des _______________________________________________ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-common-lisp-devel
