Well, it's getting quiet here (somehow), or it's just my impression ?
o AC will investigate the feasability of writing a wrapper for libusb o SieGel will investigate/port autoconf & automake o Bean will investigate/port aspell o tonyw will investigate/port BerkleyDB o Archprogrammer will investigate the currently available ports for usuability o Archprogramer will investigate the work required to port NAS.
So, those are your immediate tasks ? Anything I can help out?
I've set up the needed tasks & projects on http://dev.amigaopenoffice.org, and assigned them to the proper people, however, that doesn't mean anyone else can't help out ;)
Also, everyone with access to dev.amigaopenoffice.org has to fill in the proper details in their user account.
I have no access to that site. If someone would like to add me, go ahead.
BTW: I don't know if anyone did that already...I just compiled the single csh files with the gcc3.4 but didn't link them yet. Suddenly I have only private libraries (no dedicated 'struct DOSBase' ?? Have to check out what's wrong with my SDK). I just did it for some personal reasons and I am not sure if this can help you at all (I guess you discussed that already). It runs internal commands only and passes everthing else streight into the Amiga shell (I guess thru a System call, didn't look into the code yet), I don't know if you have access to it's local envs after that point. The command abbreviation is a pain (e.g. type Make instead of make, because otherwise finds the first (AmigaOS) command starting with 'make', which is makelink instead). The parser has to be extended to understand more sh keywords and sub shells are not possible (without a major rewrite). Command abbreviation has to be switched off, unix path names should be default (-lunix ?). So, csh requires a major rewrite. Didn't look into (the mentioned) tcsh, yet.
And no, I have no clue how a sh really works. I am no unix guru...
cheers Jürgen