On 14 March 2018 at 14:48, Anthony J. Bentley <[email protected]> wrote:
> I'll add: GitHub allows uploading files associated with tagged
> releases. Please be sure to always generate a tarball with "make dist"
> and upload it to GitHub after you've tagged it.
>
> Although GitHub does provide automatically generated .tar.gz and .zip
> archives for tags, they're unsuitable for a number of reasons:
>
> - They don't include pregenerated configure scripts, meaning the end
> user or packager must run Autoconf and Automake manually.
> - They don't have stable checksums, making them problematic for
> packaging: the files can vary depending on the versions of tar, zip,
> gzip, etc. running on GitHub's backend, and have varied this way in
> the past.
> - They don't contain Git submodules or any metadata associated with them.
>
I was hoping we could entirely do away with tarballs, but the existence of
submodules sadly makes those points partially valid.
So, don't just "make dist" and upload that tarball - actually test that you
can build from the tarball. I've had to fix up several makefiles because
new files were not added to the dist target.
But as with all the release instructions, it's also ok to just tell me
which commit hash / revision that you want to call a release, and I'll do
all the adjustments.
-- Tino Didriksen
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
