Roll new release - Githubissues

bentley commented 9 years ago

A few years ago I packaged zxing for OpenBSD. Back then, the C++ app was part of the official upstream source.

I would like to update the package (which hasn’t been updated since 2.0) to this version. But in order to do that I would be most comfortable if:

there’s a tagged release version; I don’t generally package git master on projects because in many projects it’s not stable enough.
there’s a tarball provided with the release. Github lets you do that by attaching a file to a tag with the “releases” feature. (Github‐provided .tar.gzs aren’t guaranteed to have a stable checksum, don’t include submodules, don’t provide a pregenerated configure script, and can’t be signed with a GPG key—I realize those aren’t necessarily concerns with this project, but they’re why it’s good practice in general to provide your own tarballs.)

Thanks for preserving this project!

Benjamin-Dobell commented 9 years ago

Admittedly I'm doing pretty much the bare minimum to keep this project alive - basically just providing a central place for people to submit patches. To me "versions" only really make sense if there is a proper release cycle, which unfortunately isn't something I have time to do. I guess this project is effectively in "maintenance mode" at the moment. Beyond providing a functional barcode scanner library written in C++ there are no real goals for this project. However, I am happy to merge new features etc. if they make sense.

For this reason I'd be inclined to suggest you create a fork of this project in your personal Github account. That way you can continue to pull down from upstream (this project) but add tags, adopt a versioning scheme and make releases as you see fit. When you're adding tarball and source links to the packages just link back to your own fork.

Does that seem reasonable?

simonschmeisser commented 6 years ago

I know this answer comes quite late but I'm currently having the same issue ... ie finding out what exactly zxing is and which fork should be packaged. To me nu-book version looks the most active and which should maybe be concentrated on. They even made a 1.0 release yesterday after me asking: https://github.com/nu-book/zxing-cpp/releases

Not sure how well the actual version number works for you though

glassechidna / zxing-cpp

Roll new release #29