[Bese-devel] ucw 0.2.0pre1
Marco Baringer
mb at bese.it
Sat Feb 28 14:45:29 UTC 2004
due to some issues people (myself included) were having running the
latest ucw i've put up a new tar ball of ucw in it's current state:
ftp://ftp.common-lisp.net/pub/project/ucw/ucw_0.2.0pre1.tar.gz
This tar ball contains ucw and the versions of all the latest libs i'm
using to test and develop. Testing this dist should be a simple matter
of:
1) get and unpack the tarball
2) setup asdf so that it sees the ucw_0.2.0pre1/systems/ directory (if
you have other versions of ucw, yaclml, cl-icu, portableaserve,
cl-ppcre, puri, etc. make sure those are _not_ visible). It should be
sufficent to set asdf:*central-registry* to (list
"ucw_0.2.pre1/systems") to ensure this (everything ucw needs is in the
tar ball and all the asdf systms are linked into that directory).
3) load the examples/run-examples-aserve.lisp or
run-examples-modlisp.lisp
4) PROFIT!
--------
Here's the scheme i'm currently using for building ucw dists, it may be
usefull to figure out what you need for each version:
the bese-2004 at common-lisp.net archive has a tree (support--dists--1.0)
which contains configs for the simple libraries (yaclml, arnesi,
cl-icu, etc.) and for ucw you'll find a directory for every release
i've made. Those directories (currently we have 0.1.0, 0.2.0pre0 and
0.2.0pre1) have a RELEASE file describing what it is and a build script
which pulls all the required stuff, builds up a tar ball and sends it
off to common-lisp.net (obviously only I can perform that last step).
So if you want to know what is required for using ucw 0.2.0pre1 you can
just look in ucw/0.2.0pre1/build and see what it grabs.
If anybody wants to suggest another way to create and manage these
dists i'm all ears.
--
Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
-Leonard Cohen
More information about the bese-devel
mailing list