Hi Eric,
We're OK with the DRMAA library going into sourceforge and development going there. We'd like to be able to include your changes into future Condor releases, so it'd be most helpful if you could post diffs to the Condor releases (future Condor releases will have a src/drmaa directory, which will have what's the the contrib tarball now)
I would like to announce that the new Condor DRMAA library is now in a stable state. According to the DRMAA test suite, the library is feature-complete and 'bug-free' ;-) . I am still aware of one missing mandatory feature, but I plan to discuss with the DRMAA group if this is really needed as mandatory functionality (remote sources for input files). I switched to an autoconf-based setup. I tested everything on MacOS X and Debian Sarge, but the generated Makefile *should* also work on other platforms. Please let me know how to go on from here. I could send you diffs and a generated Makefile. Anyway since I have no details about your UWCS-internal build process, I fear that something will not work on your side. Are you able to integrate the configure / make call in case of an internal build ? BTW, DRMAA expects the library to be a shared one. My version of the Makefile therefore build both a static version (for backward compatibility) and a shared library. Another major change is that all jobs are now submitted in vanilla universe. The Windows version is on the agenda, but currently there is not even a NMAKE file. The code is prepared for being compiled under Win32, but I expect a lot of remaining bugs in this environment. I would be happy if the new library will be available with the next Condor version. The release is a precondition for DRMAA working group to take the final step in the GGF standardization process, which demands 2 independent compliant versions of the spec. Thank you and regards, Peter. P.S. Nicholas did a great job. I had no problem to understand the code he developed so far.