A good place to put those scripts would be the repo I've just made: https://github.com/openbabel/maintenance
Should I tag the source differently next Monday? Also, I think I messed up the release digits in the Cmake file. I should have had .0a1 but instead have .a1. I'll upload the Windows binaries which for the most part are there. I'm thinking about including Inchi 1.05 over the next week. Matt Swain suggested automatic download and install back in June. But at this point I'm thinking to keep it simple and just do as we are already. There are sufficient changes that this is already a bit of work. -Noel On Sat, 14 Sep 2019, 15:04 Geoffrey Hutchison, <geoff.hutchi...@gmail.com> wrote: > Yesterday, I dusted off the "make a source release" script on my desktop.. > to find that it's been long enough that my new desktop doesn't have all the > various compilers to check PHP, C#, etc. > > I also discovered that GitHub is annoying about naming files matching > their auto-generated .tar.gz and .zip. Naturally, our source release has a > variety of the SWIG-generated bindings that are not stored in Git. > > There is a release tag: > https://github.com/openbabel/openbabel/releases/tag/openbabel-3-0-0a1 > > This does not include the various commits made since Noel tagged on Monday. > > Here are my working notes - I will have a modified shell script whipped up > next week: > https://gist.github.com/ghutchis/c33928316217730006790e6724993e26 > > -Geoff
_______________________________________________ OpenBabel-Devel mailing list OpenBabel-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbabel-devel
