News for hackers. Stuff that matters.
Re:CLisp needs maintainers by jordigh on Friday May 08, 2015 @06:36AM (#9510845)
Well, I just started reading Land of Lisp a few weeks ago. It recommends CLisp. I'm quite new to all of lisp, so, let's take a look:

    $ hg clone http://hg.code.sf.net/p/clisp/clisp
Wow, that took a long time to clone. How big is the thing?

    $ du -hs clisp
    147M        clisp

    $ cd clisp
    $ hg branches
    default                    15611:5c63938ef493
Hm, a moderate-sized repo, only 15611 commits and no branching to speak of. Let's look at the latest commits,

    $ hg heads
    changeset:   15611:5c63938ef493
    tag:         tip
    user:        Sam Steingold <[email protected]>
    date:        Wed Oct 22 12:04:12 2014 -0400
    summary:     Fix bug#668 posix:file-state always return NIL for :rdev
What! Last commit was from October last year? Clearly development has slowed to a standstill. Who is generally in charge around here nowadays?

    $ hg churn -r "date('2010 to today')"

    sds                        313529 **************************************
    [email protected]             194383 ********************
    vtz                          2723 *
    ampy                          801 
    haible                        758 
    [email protected]    627 
    [email protected]            279 
    [email protected]               239 
    cvs2hg                         46 
So for the past 5 years, it's been almost all the work of sds, Sam Steingold. Huh. I was expecting Bruno Haible to still be involved, but he seems to be doing almost nothing nowadays. Well, it's not unusual for a free project to be the labour of only a single person, but it's typical to have a lot of small drive-by contributions. Almost nobody except sds has done anything for CLISP for the last five years, which could explain why there have been no releases. But there's been a lot of work being done! Look at all those lines of code that have been modified! Maybe all they really need is a release manager.

Well, does the thing build right now?

    $ ./configure
    ...
    ./configure: libsigsegv was not detected, thus some features, such as
      generational garbage collection and
      stack overflow detection in interpreted Lisp code
    cannot be provided.
    Please install libsigsegv like this:
    ...
Okay, fine, I'll install it. Let me try again,

     $ ./configure
    ...
    ./configure: libsigsegv was not detected, thus some features, such as
      generational garbage collection and
      stack overflow detection in interpreted Lisp code
    cannot be provided.
    Please install libsigsegv like this:
    ...
What? Didn't I just do that?

    $ apt-cache policy libsigsegv-dev
    libsigsegv-dev:
      Installed: 2.9-4
      Candidate: 2.9-4
      Version table:
         2.10-4+b1 0
             -1 http://ftp.ca.debian.org/debian/ unstable/main amd64 Packages
     *** 2.9-4 0
            500 http://ftp.ca.debian.org/debian/ wheezy/main amd64 Packages
            100 /var/lib/dpkg/status
Okay, maybe my version of libsigsegv is too old. But a version newer than Debian's oldstable is mighty demanding of a package whose development has slowed down to nothing. So at this point I'm considering if I want to debug their build system or not. I might. Or perhaps someone else will. My conclusion is that CLisp development is almost dead, yet there certainly is something worthwhile releasing here since the last release in 2010.
Re:CLisp needs maintainers by rjsw on Friday May 08, 2015 @07:04AM (#9510903)
And that is why people shouldn't use configure [1].

[1] https://www.varnish-cache.org/docs/2.1/phk/autocrap.html

Re:CLisp needs maintainers by taylanub on Friday May 08, 2015 @10:41AM (#9511944)
>Some day when I have the time, I will rip out all the autocrap stuff and replace it with a 5 line shellscript that calls uname -s.

And packagers will everywhere will hate you for it.

I've recently written many GNU Guix package recipes, and packages using Autotools are the ones I tend to have the least headaches with. CMake and Waf are so-so I think, perhaps lacking in maturity, but I didn't have that much experience with them. Custom/hand-written Makefiles and ./configure scripts are the worst.

Just learn Autotools, get over the fact that they contain backwards-compatibility crud (that you can just ignore, or how does it hurt you?), and stop the FUD. Even if only targeting GNU and BSD systems, there is already enough diversity and library detection boilerplate to make it worth using a proper build system, and Autotools is the most mature one out of the bunch.

It's even more important for unconventional systems like Nix/Guix where software is to be built in very special ways, where hard-coded assumptions in build systems hurt, especially if a custom one; if it's a known one then even if hard-coded it will probably conform to some typical pattern of use of that build system so one can use tooling to automatically fix packages using that build system, and in the case of Autotools that isn't necessary in first place because everything is parameterized and flexible to hell and back.

Also please do use pkg-config. Like Autotools, it's not perfect either, but I could write another two paragraphs on how helpful it is in bringing consistency, toolability, etc. into build/packaging systems...

Re:CLisp needs maintainers by haberman on Friday May 08, 2015 @12:22PM (#9512539)
My entire build can run in less time than a ./configure script.

It doesn't require developers to run ./autogen.sh, or to have autotools installed (in their correct versions).

It doesn't contain obscene amounts of indirection, where the actual libraries live in a hidden directory called .libs (looking at you, libtool).

It doesn't make you write m4, or Makefile.am files with all these magic incantations. It doesn't make you delve into the guts of these crufty systems when things don't work the way you expect.

If you want build systems to satisfy your use cases, publish some doc of best practices and capabilities that all build system interfaces should provide. If I'm convinced I'll be happy to conform to the interface you need. But there is no way you're going to convince me that everyone needs to just keep using autotools (a specific implementation) forever. I hate them.

I mean, by that logic, why are you doing something new like GNU Guix when everybody already knows/uses APT, RPM, BSD ports, etc? "Just learn [them], get over the fact that they contain backwards-compatibility crud (that you can just ignore, or how does it hurt you?), and stop the FUD."

Or maybe it is worth breaking with the past sometimes, when you think you can do better.

Re:CLisp needs maintainers by taylanub on Monday May 18, 2015 @10:04AM (#9564454)
Late reply but:

All of the things you list are annoyances with crud that exists to satisfy this or that use-case which I suppose you personally don't need, which doesn't mean they don't have purposes. I would also say they are all minor annoyances. Your builds run faster than a ./configure script? Not building particularly large projects I suppose. Installing autotools? Big deal! I don't know when one needs to write m4, but the Makefile.am format looks rather clean and minimal to me; I don't see how you could have something much cleaner without losing a lot of generality. And having to delve into the guts of some obscure system is exactly what I had to do a few times because some piece of software refuses to keep with the convention and just use Autotools.

The documentation you ask for is idealistic and unrealistic. GNU Autotools are free software, and with decades-old proven maturity; I see no reason not to use them. The only pseudo-reasons I see are NIH, FUD, etc.; the usual.

GNU Guix (and before that, Nix) is fundamentally different from all other package managers, so that analogy makes no sense here unless you have some radically different innovative build system.

Re:CLisp needs maintainers by jordigh on Friday May 08, 2015 @11:14AM (#9512123)
One of the nicer things about autotools is that they handle cross-compilation very well. Most other build systems have a huge problem with it.
Re:CLisp needs maintainers by jordigh on Friday May 08, 2015 @07:38AM (#9510984)
Turns out that configure was just caching the past test for libsigsegv. I cleared the cache and was able to build. The test suite ran for a good chunk of time but segfaulted.

So it doesn't look like CLisp is beyond all hope, just a little lonely.

Re:CLisp needs maintainers by masukomi on Friday May 08, 2015 @09:17AM (#9511485)
Yeah, I brew installed it on my mac and, despite the world seeming to prefer SBCL I've been rather happy with it.
Re:CLisp needs maintainers by josteink on Friday May 08, 2015 @08:29AM (#9511175)
> So for the past 5 years, it's been almost all the work of sds, Sam Steingold. Huh. I was expecting Bruno Haible to still be involved, but he seems to be doing almost nothing nowadays. Well, it's not unusual for a free project to be the labour of only a single person, but it's typical to have a lot of small drive-by contributions. Almost nobody except sds has done anything for CLISP for the last five years

This is how you smell a future dead project.

If only one person has done anything significantly, with nobody around to "pick up the chops" and learn the code-base, chances of anyone willing to pick up 147MB of sources and claiming responsibility for it is pretty slim.

On the flip side, we do have a gazillion free Common Lisp implementations around. If this one falls dead, will the Common Lisp community have lost anything of significance?

From what I can tell, the only ones "losing" something here would be GNU losing a thing they can claim being made by them, a feather from their highly featured hat.

But my general impression is that GNU is already critically understaffed anyway, so it might actually do them some good, and avoid having dead-weight like this steal resources from their remaining projects.

Opinions?

Re:CLisp needs maintainers by zachbeane on Friday May 08, 2015 @08:45AM (#9511261)
GNU CLISP does not get any resources, human or otherwise, from the GNU project. If Sam stops working on CLISP, he's not going to start working on GNU Emacs or gdb instead.
Re:CLisp needs maintainers by coldtea on Friday May 08, 2015 @08:50AM (#9511298)
>But my general impression is that GNU is already critically understaffed anyway, so it might actually do them some good, and avoid having dead-weight like this steal resources from their remaining projects.

GNU is not an organization that employs or assigns people to work on specific projects (with very few exceptions).

Re:CLisp needs maintainers by patal on Friday May 08, 2015 @07:37AM (#9510980)
Don't know about libsigsegv. configure mumbles something about needing libsigsegv-2.10, but I've got 2.10-2 installed all right. To be fair, configure also suggests a very special installation procedure, which I haven't tried.

Anyway, the configure script succeeds with "./configure --ignore-absence-of-libsigsegv", a subsequent make, too. This is on Trusty.

Nice conclusion.