Debian packaging for Clasp about clasp HOT 10 CLOSED

Food for thought - can Boost Build generate tarballs?
I have only found this - http://lists.boost.org/boost-build/2009/08/22270.php

from clasp.

Ok, here are instructions on testing the debian packaging, which is currently still mostly broken.

1. Clone the main clasp repos from Github. I.e.

    git clone git://github.com/drmeister/clasp

2. cd into that directory

     cd clasp

Clone into that directory.

     hg clone http://bitbucket.org/faheem/clasp-debian debian

3. Run the following command.

     ./debian/rules get-orig-source

4. Go up one level, and cd into clasp-0.1

    cd ..; cd clasp-0.1

5. Install the build dependencies given in debian/control.

    sudo apt-get install ...

6. Run the debian build command debuild. Note that this creates a log by default

    debuild -uc -us

Post questions etc to this issue.

from clasp.

My current blocker is #17

from clasp.

The workaround suggested by Edward for #17 worked.

The build is currently erroring out at
https://gist.github.com/765eaf4ce13915215882

The problem is that I'm putting the build under tmp. I.e.

jessiechroot)faheem@orwell:/usr/local/src/clasp/clasp/tmp$ ls  
Contents  bin

So, the build is looking in the wrong place for this. I have the setting:

export CLASP_BUILD_TARGET_DIR=$(ROOT_DIR)/tmp

where ROOT_DIR is the top level of the source code repos.
That's the only place I have configured it.

Actually, this might be a good time to figure out where to install the files in the system. I'll need this information to construct the deb package.

from clasp.

The CLASP_BUILD_TARGET_DIR must have the last directory name be "clasp".
export CLASP_BUILD_TARGET_DIR=$(ROOT_DIR)/tmp doesn't end in "clasp" and will not work
export CLASP_BUILD_TARGET_DIR=$(ROOT_DIR)/tmp/clasp does end in "clasp" and will work.

This is because when Clasp starts up, it uses the path of the executable to identify directories in the Clasp target directory. It expects the directory above where he executable is found to be named "clasp".

Also, the build log is very long. You could remove the "-v" option from your local.config file to make it more concise.

from clasp.

I now have a working deb, There is still the following problem with the deb: The deb sets up a symlink to
the actual executable.

$ ls -lah /usr/bin/clasp-boehm 
lrwxrwxrwx 1 root root 30 Oct 13 05:28 /usr/bin/clasp-boehm -> ../lib/clasp/bin/clasp_boehm_o

but calling the symlink gives the following error.

$ rlwrap clasp-boehm   

Could not find the root directory of the cando application bundle.
 It must contain the word "clasp".

../../src/core/foundation.cc:285 dbg_hook(...) was called
rlwrap: warning: clasp-boehm crashed, killed by SIGSEGV.
rlwrap itself has not crashed, but for transparency,
it will now kill itself (without dumping core) with the same signal

warnings can be silenced by the --no-warnings (-n) option
Segmentation fault

However, calling the binary executable directly works.

(jessiechroot)faheem@orwell:~$ rlwrap /usr/lib/clasp/bin/clasp_boehm_o 
Starting Clasp 0.1... loading image... it takes a few seconds
Could not find pathname: /home/faheem/.clasprc
Top level.

Hopefully this will be fixed soon.

from clasp.

After increasing swap to 8gb (from 4gb), I just built the mps version successfully. I now have a complete build.

This machine has 16gb RAM and now 8gb swap.

from clasp.

Thank you for all your hard work! Is this something that is releasable to dummies like me who are sucker enough to try it out on their own local machine? ;-)

from clasp.

On Wed, 15 Apr 2015, Raoul Duke wrote:

Thank you for all your hard work! Is this something that is releasable
to dummies like me who are sucker enough to try it out on their own
local machine? ;-)

Hi,

This version of the Debian packaging was for an old and probably out of
date version of Clasp. I don't think building the packaging itself would
be a problem, but you might want to ask Chris when he is going to be
releasing the next version, because the packaging will need to be changed
for that version. As you are probably aware, Clasp is still changing fast.

                                                      Regards, Faheem

—
Reply to this email directly or view it on GitHub.[ACcHR9ksltNndcnDYqK1y0HHHasAeWbBks5n_pPigaJpZM4Csl-S.gif]

from clasp.

Given Clasp's instability, frequent changes and updates, heavy dependencies, and general bulkiness I think it's still premature to include it in any distributions. We can reopen this once things have levelled out.

from clasp.