<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2">
</HEAD>
<BODY>
Hi, Ian, and welcome. It sounds like you will be able to make some nice contributions.<BR>
I am the maintainer, so I am the main person to coordinate with. I will be out of email range<BR>
today, but we can discuss it more tomorrow. The original authors are on the "devel" list,<BR>
and we can re-open the licensing conversation with them.<BR>
<BR>
There are some known PPC problems; Andrew Blumberg and others are working on that,<BR>
and I'm sure they would welcome your help.<BR>
<BR>
Can you give me the link about elephant being down? I don't know what that means<BR>
and would like to find it and repair it. As far as I know, elephant has not been down,<BR>
and I know of no reason why you shouldn't be able to sign up to the list.<BR>
<BR>
On Tue, 2006-01-17 at 16:03 -0500, Ian Eslick wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Aside from the common-lisp.net pointer to elephant being down (.org </FONT>
<FONT COLOR="#000000">works) I have been unable to sign up to the developers list and have </FONT>
<FONT COLOR="#000000">some patches to make the Allegro bdb version of elephant on Mac OS X </FONT>
<FONT COLOR="#000000">more robust (at least in my particular setup) that I would like to submit.</FONT>
<FONT COLOR="#000000">I'm planning to use elephant for a large data collection effort and </FONT>
<FONT COLOR="#000000">expect I'll need/desire to contribute to the system as I proceed in </FONT>
<FONT COLOR="#000000">using it for this application so wanted to find out who are the key </FONT>
<FONT COLOR="#000000">people to coordinate with for checking in code and get on the list so I </FONT>
<FONT COLOR="#000000">can stay up to date with development.</FONT>
<FONT COLOR="#000000">I'm using the recent 0.4.0 release with version 4.3 of sleepycat under </FONT>
<FONT COLOR="#000000">Allegro 7.0 on a PPC G4 PowerBook running Mac OS X 10.4. The approach </FONT>
<FONT COLOR="#000000">to serialization of strings in 0.4.0 didn't work for me. I suspect it's </FONT>
<FONT COLOR="#000000">a byte ordering problem in the unicode encoding. On my PPC under </FONT>
<FONT COLOR="#000000">allegro the native-to-string failed to work (returned all '???' - a good </FONT>
<FONT COLOR="#000000">indication of byte order problems) with the default copy in serializing </FONT>
<FONT COLOR="#000000">2-byte characters. Also in my version of allegro strings are stored </FONT>
<FONT COLOR="#000000">internall as 1-bit entities but the :ics features is still set so :ics </FONT>
<FONT COLOR="#000000">does not categorically imply 2-byte unicode. Not sure if this is a </FONT>
<FONT COLOR="#000000">Franz feature or a bug. I also added a little bit the build process to </FONT>
<FONT COLOR="#000000">support .dylib builds under Mac OS X and some vendor variances in </FONT>
<FONT COLOR="#000000">*features* (Allegro doesn't provide the :darwin feature, only :macosx). </FONT>
<FONT COLOR="#000000">etc, etc. I have little patches for all this.</FONT>
<FONT COLOR="#000000">My setup passes all tests on bdb except migration because I haven't </FONT>
<FONT COLOR="#000000">installed Postgres yet. I'll do that at some point and perhaps check </FONT>
<FONT COLOR="#000000">out MySQL.</FONT>
<FONT COLOR="#000000">I also want to discuss the LLGPL license vs. the GPL license for systems </FONT>
<FONT COLOR="#000000">based on the code. Now that we can backend to different SQL platforms </FONT>
<FONT COLOR="#000000">there it would be nice to have more flexibility on using the elephant </FONT>
<FONT COLOR="#000000">lisp code which LLGPL would provide. I saw a discussion in November on </FONT>
<FONT COLOR="#000000">this but notice that the license hasn't been update.</FONT>
<FONT COLOR="#000000">Many thanks,</FONT>
<FONT COLOR="#000000">Ian</FONT>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>