[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Manpower in Debian Common Lisp Team

Hi Sébastien,

> For the last couple of years, I’ve been the most active member of the
> Debian Common Lisp Team. However, it’s becoming increasingly clear that
> my involvement is now going to be significantly reduced (lack of time,
> change of focus).

first of all, thank you so much for your (mostly lonesome)
work during the last years!

> So this email is essentially a call for volunteers. I will not
> disappear entirely, so I can certainly act as an adviser during a
> transition period. In particular, I would explain (or document) a few
> practices that I’ve been following so far (regarding version numbering
> and autopkgtests of CL libraries in particular).

I would be happy to take over some of the tasks and I would
appreciate your documenting the practices, as you mentioned,
even it is only in a 'bullet list' style.

> The most immediate task would be to update SBCL. I’ve given a try to
> packaging version 2.2.2, but got across a problem I’ve reported
> upstream (left unanswered so far):
> https://bugs.launchpad.net/sbcl/+bug/1964511
> Maybe this problem can be worked around by putting the call to sb-
> ext:set-sbcl-source-location in /etc/sbclrc, instead of trying to
> modify the Lisp image at build time (though the latter is obviously
> better).

I will start by looking into this.

Thanks again


Reply to: