[plt-scheme] Debian binary package

From: Matthew Jadud (mcj4 at kent.ac.uk)
Date: Fri Feb 16 06:09:46 EST 2007

Hi all,

We have a VMWare virtual machine that we use for introducing students to 
concurrency via robotics. It is, we find, easier for students to 
double-click install a virtual machine than to find a Linux box, install 
Player/Stage, and then a host of other software. 

We're in the process of updating that VM. We'd like it if everything we 
need on the VM was a Debian package. This includes our virtual machine 
(the Transterpreter) as well as the supporting tools, including our 
linker (the slinker) and the compiler wrapper (skroc). These are both 
tools written in MzScheme.

I realized, in making our new machine, that our tools are compiled with 
"mzc --exe", and not "mzc --exe-dir". As a result, we're not portable 
between installations. Either we can:

1. Fix our build process for skroc and the slinker, or
2. Install MzScheme on our VM, which we'd kinda like anyway.

However, I'm trying to make a quick-and-dirty MzScheme binary Debian 
package. This certainly doesn't work:

./configure --prefix <path>/deb-pkg/usr/local

because all of the executables (setup-plt, mzc, etc) get built as if 
they were sitting at "<path>/deb-pkg/usr/local".

Are there any magic incantations I can pass at configure-time to 
convince MzScheme that, really, it will end up at "/usr/local" when all 
is said and done? Or, is there an easy way to update those scripts (mzc, 
etc.) so that I can, in two steps (instead of one) create a binary 
Debian package?

Sorry for all the detail; that ran on a bit.


Posted on the users mailing list.