I would take this on, but you should know that I'd face two learning curves
in doing so:
1) Cygwin package maintenance--I've never done it before, though I was
thinking of turning my Glimpse indexer port (it was trivial) into a Cygwin
package, so learning the ins and outs of Cygwin package preparation and
maintenance would kill both these birds
2) CLISP internals--I've never been under the hood of CLISP. The last
language interpreter / compiler I worked on was XSB
(<http://xsb.sourceforge.net/>), which also is also uses a byte-code
compile and interpret scheme, so I do have some background with this sort
If you find these circumstances acceptable, then I'll undertake to learn
about Cygwin packaging.
You should inform me (or refer me to the necessary information) about the
CLISP CVS repository, the version / tag naming scheme and which is to be
used as the basis for a new Cygwin package, how the CLISP principals work
w.r.t. to collaborative development, how / when to track ongoing
developments by the CLISP developers, other lists I should subscribe to, etc.
I just saw the 2.29 release announcement, so I assume this is the target
for a Cygwin release.
Mountain View, CA USA
At 09:15 2002-07-25, Sam Steingold wrote:
> > * In message <126.96.36.199.2.20020424084257.027689b8@...>
> > * On the subject of "Re: [clisp-list] Cygwin feature"
> > * Sent on Wed, 24 Apr 2002 09:00:24 -0700
> > * Honorable Randall R Schulz <rrschulz@...> writes:
> > I use Cygwin extensively, so the Cygwin version would interest me
> > greatly. I don't doubt the Cygwin principals would accept a CLISP
> > package into the Cygwin contributed software.
>Would you like to maintain the Cygwin CLISP package?
>Sam Steingold (http://www.podval.org/~sds) running RedHat7.3 GNU/Linux
><http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
>A man paints with his brains and not with his hands.