Path: g2news1.google.com!news1.google.com!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nx02.iad01.newshosting.com!newshosting.com!news2.euro.net!news-out2.kabelfoon.nl!newsfeed.kabelfoon.nl!xindi.nntp.kabelfoon.nl!newsfeed00.sul.t-online.de!t-online.de!inka.de!raven.inka.de!not-for-mail
From: Josef Wolf <j...@raven.inka.de>
Newsgroups: comp.lang.lisp
Subject: Re: common-lisp-controller vs. asdf-install
Date: Fri, 3 Sep 2010 13:35:00 +0000 (UTC)
Organization: PPCGer
Lines: 49
Message-ID: <slrni81uc4.vu7.jw@raven.wolf.lan>
References: <slrni7thrc.b07.jw@raven.wolf.lan> <87vd6poyep.fsf@puma.rapttech.com.au>
NNTP-Posting-Host: localhost.localdomain
X-Trace: raven.wolf.lan 1283520900 9871 127.0.0.1 (3 Sep 2010 13:35:00 GMT)
X-Complaints-To: news@raven.inka.de
NNTP-Posting-Date: Fri, 3 Sep 2010 13:35:00 +0000 (UTC)
User-Agent: slrn/0.9.8.1pl1 (Linux)

On 2010-09-01, Tim X <t...@nospam.dev.null> wrote:
> Josef Wolf <j...@raven.inka.de> writes:
>> Hello,
>> I see that debian/ubuntu use common-lisp-controller to package
>> libraries. Cliki, OTOH, seems to prefer asdf-install. Unfortunately, many
>> packages are missing from debian/ubuntu. What would be the proper way to
>> install additional packages on those machines? Install asdf-install in
>> parallel? Or tell common-lisp-installer how to install asdf-install'able
>> packages?
>
> Well, it all depends on what your requirements are. 

I am trying to learn lisp. In order to get beyond trivial examples, I'd like
to try some still simple, but real useful examples, involving some existing
libraries which don't come pre-packaged with debian.

> The clc framework is really good if you plan to run multiple lisp
> implementations and want to have all your libraries available for all of
> them. 

As a beginner, I'm pretty much happy with whatever is easy to install.

> You can have both clc and asdf packages

Yeah, since clc uses asdf under the hood, that'd be expected.

> and provided you follow a few
> key steps, it will work well. It isn't an either or situation. However,
> it can become a pain if you don't follow a consistent path. 

The problem is, I can't find any information about what those "key steps"
are.

> I recommend looking at 
> http://pkg-common-lisp.alioth.debian.org/clid/clid.html/index.html

Thanks for the pointer. But this seems to be a policy that tells package
maintainers how to create their packages. No pointers where to put libraries
I download from cliki.net. Don't look like a "user manual" to me.

> I use the debian packages if available AND they are the version I need.
>
> I use ASDF when they are not available or I want a later version than
> the current debian one. 
>
> I use ASDF in my projects to handle loading what I need. 

So where do you extract the downloaded tarball and and where do you put the
symlinks to the asd files? How do you tell clc about that?