Mailinglist Archive: opensuse-packaging (266 mails)

< Previous Next >
Re: [opensuse-packaging] Common LIsp packaging
On Wed, Nov 21, 2012 at 5:58 PM, Togan Muftuoglu <toganm@xxxxxxxxxxxx> wrote:
On 11/20/2012 12:14 AM, Alex Naumov wrote:

Yes, good idea, but we have not such macro file for Lisp until now.
And the question is... where we can add it?
For perl or python it's easy, because we put it to package of
interpreter: perl or python-base, but for Common Lisp there are
different interpreters/compilers implementation. For example, clisp or

Now I'm curious if you also get feedback from people who know something
about Lisp ;-)

I'm waiting critic about using ASDF ;-)

Or maybe let the lisp implementation to have a initialization file and
solve the fasl problem via that. (see sbcl documentation about FASL
Format). Currently sbcl in the factory does not have a system wide
initialization, but could be added if needed.

Yes, it will solve the problem in case using SBCL, but what's about
another Lisp interpreters?
Do you want to use SBCL as a main compiler, that should be installed always?

On Thu, Nov 22, 2012 at 1:51 PM, Togan Muftuoglu <toganm@xxxxxxxxxxxx> wrote:
On 11/20/2012 12:14 AM, Alex Naumov wrote:
Hi Christian,

thanks a lot for your reply!

On Mon, Nov 19, 2012 at 9:52 PM, Christian Boltz <opensuse@xxxxxxxxx> wrote:

Am Montag, 19. November 2012 schrieb Alex Naumov:
The first version of it you can find there:
(please discuss here before edit something in wiki)

I don't know anything about Lisp, but... (quoting from the wiki page)

| BuildRequires: common-lisp-controlle
| Requires: common-lisp-controller
| Requires(post): common-lisp-controller
| Requires(preun): common-lisp-controller

Before putting common-lisp-controller as a requriment how about
providing the package.

Maintainer needed? ;-)

On Thu, Nov 22, 2012 at 1:51 PM, Togan Muftuoglu <toganm@xxxxxxxxxxxx> wrote:
If one builds a package based on this sample spec
it sure will fail as there is no such package and having it in your home
project does not count to have it in a guideline for the entire project.

I did not send request, because I still not satisfied about quality
and, as I said, I'm going to use quicklisp.

Stumpwm, that I have already, works well, but I would like to make it
cleaner and check/test it again.

To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups