Packaging CL libs and apps for debian

[Dimitri Fontaine]

Faré <fahree at gmail.com> writes:
> That's fairly old. In practice, I recommend upgrading to the latest stable
> when having trouble such as yours.

I needed to upgrade for a test program I made using
command-line-arguments that requires uiop…

>> Is that the intended way to use a debian packaged CL lib?
>>
> I believe so, though my understanding is the debian package CL
> libraries are not that well maintained anymore. These days, all the
> cool kids use quicklisp. Now, if you could write an automated
> quicklisp to debian packager...

I got it all to work together and made a very simple binary image using
drakma to act as curl to check that I was on the good path. Then I added
some more libs, as you can see at

  http://pgsql.tapoueh.org/cl-debian/

I'm not quite sure Quicklisp to debian package is the way to go, because
of the Quicklisp release policy that I don't know of. Will talk about
Xach about that.

Again, my goal here is to package all the dependencies I need for
pgloader and other CL programs I want to ship in debian, and I want to
ship them in source and binary format. What I want is to be able to
buildapp pgloader from sources all found within the debian repositories.

> Back in the bad old days, c-l-c was trying to have a system cache.
> This turned out to be a configuration and security nightmare.

Ok. I don't think the docs have been updated to reflect what's currently
happening.

> In the past, there have been bugs with respect to following symlinks,
> handling directory pathnames without a trailing slash, etc., etc.
>
> I would recommend upgrading ASDF over trying to debug an old one.

It wasn't even down to asdf here, I got it fixed, and I'm now in a
position to be able to finish my libs packaging then build pgloader out
of cl-* debian packages.

Regards,
-- 
dim