official website went offline? about oniguruma HOT 16 CLOSED

Yes, all of the information that was on the geocities website is now present in this github repository, including the documentation (doc/), examples (sample/), etc. It makes it easier to work with and contribute to. :)

Is there anything missing?

from oniguruma.

Glad to hear that.
As there were no announcement of GitHub migration, some people couldn't find this repo and started to look for a replacement: jqlang/jq#936

If you can, could you please add git tags to the release commit, so that we can easily download stable tarballs by URL like this: https://github.com/kkos/oniguruma/archive/v5.9.6.tar.gz (where v5.9.6 is a tag for commit 87b1d7f, for example)

from oniguruma.

Done, that link is now valid. Thanks for reporting!

from oniguruma.

Thanks a lot!

from oniguruma.

Submitted upstream (to homebrew) as Homebrew/legacy-homebrew#43581.

from oniguruma.

Thank you very much.

from oniguruma.

Hey @kkos, check out Homebrew/legacy-homebrew#43581 (comment) - do you want to generate the autoconf/automake files or add that as a dependency? (I'm leaving that decision up to you. :)

from oniguruma.

Please add those files into the repository if it is impossible to include those files in a generated tarball.

from oniguruma.

Alternatively, instead of using auto-generated tarballs, you can attach your own (hand-generated) tarballs to a specific tag by clicking Add release notes link, just FYI.

from oniguruma.

Thank you.
I tried it. Is it OK?

from oniguruma.

The first line of README file of the attached tarball is README 2007/05/31, whereas the auto-generated tarball says README 2015/08/04.
Preferably manually attached tarballs be generated from the commit the tag points to. In this case, it is better to get auto-generated tarball, decompress, run autoconf (and other processes needed for release archive), compress, then attach it to the release note.

from oniguruma.

Hmm... the onig-5.9.6.tar.gz is already released tarball in my old Geocities page.
So I don't want to change the contents.
5.9.6 tag position should be moved to 87b1d ?

from oniguruma.

5.9.6 tag position should be moved to 87b1d ?

I think that is a reasonable choice in this case.

from oniguruma.

@kkos I agree. For future releases, I think it's a good idea to add the missing files to the repository itself like you said so that tarballs can be generated automatically.

from oniguruma.

I have moved v5.9.6 tag to 87b1d.
I will add generarted files into repository in the next release.

from oniguruma.

Thanks!

from oniguruma.