Prev: AUTHENTIC DESIGNER HANDBAGS & ACCESSORIES WWW.VOGUELANDE.COM CHANEL LOUIS VUITTON
Next: Re^2: slime errors in cmucl?
From: Norbert_Paul on 6 Apr 2010 11:59
Raymond Toy wrote:
> I don't have a Debian system so I don't know, but is the layout
> different from what official tarballs from common-lisp.net? (CMUCL's
> layout is something like<path>/bin/lisp and<path>/lib/cmucl/<more
> cmucl stuff>.)
Did it. Now slime is broken.

> Maybe you can install the tarballs somewhere and have a simple script
> call that for now. When there's a Debian update, point the script to
> the Debian location.

Debian has something called common-lisp-controller.
This is more or less what one should do to install a new lisp on Debian ...
https://alioth.debian.org/scm/viewvc.php/*checkout*/clc/DESIGN.txt?revision=1.2&root=clc
....be he a package or a human.

I'll keep trying.

Norbert
From: Tamas K Papp on 6 Apr 2010 12:00
On Tue, 06 Apr 2010 17:59:34 +0200, Norbert_Paul wrote:

> Debian has something called common-lisp-controller. This is more or less
> what one should do to install a new lisp on Debian ...
> https://alioth.debian.org/scm/viewvc.php/*checkout*/clc/DESIGN.txt?
revision=1.2&root=clc
> ...be he a package or a human.

I disagree, CLC was more of a source of a headache for me than an
useful layer. My Lisp experience on Debian has been the smoothest
with clbuild (for SLIME, libraries) and an SBCL compiled from source.
I only use the Debian-packaged SBCL to compile the latter.

Best,

Tamas
From: Raymond Toy on 6 Apr 2010 12:49
On 4/6/10 11:59 AM, Norbert_Paul wrote:
> Raymond Toy wrote:
>> I don't have a Debian system so I don't know, but is the layout
>> different from what official tarballs from common-lisp.net? (CMUCL's
>> layout is something like<path>/bin/lisp and<path>/lib/cmucl/<more
>> cmucl stuff>.)
> Did it. Now slime is broken.

Insufficient info to fix anything. FWIW, I have a script cmulisp that
calls some random version of cmucl from common-lisp.net. This works
just great with slime, but I do need to be a little careful with my init
files if the version is sufficiently different from previous versions.

Ray
From: Rupert Swarbrick on 6 Apr 2010 16:34
Norbert_Paul <norbertpauls_spambin(a)yahoo.com> writes:

> What would a Debian-compliant replacement of cmucl by the latest release
> look like?

Ok, so it's probably too late to be useful for you, but in case anyone's
reading the intawebs in the future:

Debian packages are built from (vanilla upstream) source tarballs by
unpacking the tarball, applying a patch and calling some magical build
scripts. The patch generally just adds a debian/ directory, which
contains information on how the package should be built (this bit's
usually trivial), and how it should be installed and integrated into the
system in a way that can be uninstalled again.

If the newest upstream sources are similar to those for which the debian
patch was created, you're in luck: Download the vanilla files and then
apply the debian patch. Then take note of what you want the new version
string to be and cd into the debian/ directory that got created. Now you
can probably type "dch -v <myversion>" [1], which will create a new
version in the changelog.

Go back up to the main directory and call "dpkg-buildpackage" [2] and
with a bit of luck a brand spanking new version of the package will be
built. (This assumes that I got everything right...) Note that you might
want to do something like "apt-get build-depends cmucl" to pull all the
libraries that debian thinks you need to build it.

Finally you can "sudo dpkg -i <mynewcmucl.deb>" or something to install
it.

You can find the relevant debian tarballs and diffs at the package page,
which seems to be [3]. Since I've almost certainly made at least one
mistake in the above, you might want to look at the debian new
maintainers guide [4]. This is sort of oriented to people that are
building official packages, but of course the technical details are all
identical.

I hope this is of some use,

Rupert




[1] dch is in the devscripts package
[2] dpkg-buildpackage is in the dpkg-dev package
[3] http://packages.qa.debian.org/c/cmucl.html
[4] http://www.debian.org/doc/maint-guide/
From: Norbert_Paul on 7 Apr 2010 02:47
Thank you for the info, i'll try this later.
But for now I have a working, yet possibly messy, environment which I will
use to continue on my work.

Norbert

Rupert Swarbrick wrote:
> Norbert_Paul<norbertpauls_spambin(a)yahoo.com> writes:
>
>> What would a Debian-compliant replacement of cmucl by the latest release
>> look like?
>
> Ok, so it's probably too late to be useful for you, but in case anyone's
> reading the intawebs in the future:
....
First  |  Prev  | 
Pages: 1 2 3 4 5 6
Prev: AUTHENTIC DESIGNER HANDBAGS & ACCESSORIES WWW.VOGUELANDE.COM CHANEL LOUIS VUITTON
Next: Re^2: slime errors in cmucl?