On Tue, Nov 27, 2012 at 7:33 PM, Togan Muftuoglu <toganm@opensuse.org> wrote:
On 11/27/2012 07:02 PM, Alex Naumov wrote:
On Tue, Nov 27, 2012 at 8:47 AM, Togan Muftuoglu <toganm@opensuse.org> wrote:
I would add such a config option to sbcl package with the next version that is installed as a sample in the documentation along with a README file, and let the user decide how to use it.
Sorry, I did not get it. Why SBCL, and not CLISP or GCL or another compiler/interpreter? Why not CLC?
Simple
I am one of the maintainers for sbcl but not for clisp, therefore I can add the asdf solution to sbcl easily. clisp maintainer needs to solve the problem if s/he wants also.
Ok, then we can use SBCL as a default openSUSE Common Lisp compiler.
I did not send request, because I still not satisfied about quality and, as I said, I'm going to use quicklisp.
Hence this proves my concern, I would prefer to have quicklisp also, but on the other hand the guideline should take it into consideration what is available in the distribution not things available in users' home repositories.
Sure. The idea of using quicklisp is automatically to check and download missing software components (all needed dependencies). So, first, we download quicklisp.lisp file: $ curl -O http://beta.quicklisp.org/quicklisp.lisp We can use "download_url" service for that. After that we run compiler and install our package (in my case it's "stumpwm"): $ sbcl --load quicklisp.lisp --eval "(quicklisp-quickstart:install)" --eval "(ql:add-to-init-file)" $ sbcl --eval "(ql:quickload \"stumpwm\")" This will download and install a lot of CL packages needed for stumpwm. After that we can start stumpwm. The problem is that such features will never support for OBS (in the .opensuse.org instance), I guess. The reason is that for one the builds would not be reproducable anymore. Also it would create a number of security problems. It would be for example possible to attack oS servers and also external servers. As I can see, another distros still uses old way - ASDF. In this case all needed libraries/dependencies are in the same repositories like usual. I have no idea how to do that for quicklisp packages... I see one (and very bad) way to do that: just put all quicklisp stuff to %post and use BuildRequires: -post-build-checks I hope somebody can help to find another solution for that. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org