Preliminary Debian packaging for Clozure Common Lisp (ccl.clozure.com)
Faheem Mitha <faheem at faheem.info> writes:
>>> 2) The main outstanding issue is how to handle the bootstrapping
>>> issue, namely that CCL is not in Debian, but requires CCL to compile.
>> For sbcl I do bootstrapping with a crossbuild from another
>> architecture .. building just a non-packaged version and using that to
>> bring up the package. Once there is a version in the archive everything
>> works automatically. So ideally I can build the first package with a
>> locally installed ccl (e.g. in /usr/local/bin, ..). sbcl's debian/rules
>> has some magic now to do this (and the last commit is totally messed up
> Could one just use upstream binaries instead? CCL has upstream
> binaries available, which I use to initially build my Debian package,
> for at least i386 and amd64. My package currently does not attempt to
> build on any other architecture, because I can't test it.
Jep that'll work you just need to provide the sponsor with enough
information to bootstrap the package with binaries from a sane enough
source (and I'd consider upstream such a source). Best to add this
information to debian/README.source IMHO.
>> I guess bootstrapping only needs to be done once and later versions of
>> ccl can be built using the version that is then included in Debian?
> Well this is precisely my question to the CCL developers. So far, I
> have not got a response. See the thread
If it's not possible to build ccl with a (slightly) older version of ccl
it'll be pain to maintain. One can (as Peter noted in the thread) go the
cmucl route but that'll need the maintainer (you) to do bootstrapping
every time, the sponsor to do bootstrapping every time and for evvery
architeccture you might want to support (as you might have noticed cmucl
is only available on linux-i386 and not even on 64bit systems)
9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer