[Xastir-dev] New release coming up soon, old release "regenerated" on Github, call for discussion

[Tom Russo]

On Wed, Feb 07, 2018 at 11:52:48AM -0700, we recorded a bogon-computron collision of the <russo at bogodyn.org> flavor, containing:
> I think I am days away from pushing out an Xastir 2.1.0 stable release, 
> which will pretty much be exactly the code that's at the head of master
> right now.
> 
> To test out the release mechanism on github, I've gone ahead and created
> a "new" Xastir 2.0.8 release branch (branched from the xastir208 tag that
> was used for the SourceForge stable release), bootstrapped it, pushed it to
> github, tagged it with "Xastir-Release-2.0.8", and told GitHub to call it
> a release.  

[...]

> The tarball for a ready-to-build version 2.0.8 of Xastir could be downloaded
> just by wgetting 
> 
>    https://github.com/Xastir/Xastir/archive/Xastir-Release-2.0.8.tar.gz 
> 
> a Zip file could be gotten as:
> 
>    https://github.com/Xastir/Xastir/archive/Xastir-Release-2.0.8.zip

> One thing to note:  These files unpack into "Xastir-Xastir-Release-2.0.8,"
> an artifact of how Github creates tarballs.  I put "Xastir-" into the tag
> name so that when the release tarball is downloaded it wouldn't just be
> called "Release-2.0.8", but github has helpfully bundled it up with the
> project name prepended.  This should not be a problem, and I've seen other
> projects do their releases this way.  But it does mean that the extracted
> files have an extra "Xastir-" in the top-level directory name.

I have already gotten one bit of heartache from a package maintainer about this,
so I'm going to change it.  I've already pushed an additional git tag
for the "regenerated" 2.0.8 release so you can test it out.  At this stage,
both the URL I put above *and* the one below will work.

If you use the URL:

https://github.com/Xastir/Xastir/archive/Release-2.0.8/Xastir-Release-2.0.8.tar.gz

then you will get a file called Xastir-Release-2.0.8.tar.gz, but whose contents
are in the directory "Xastir-Release-2.0.8" and not "Xastir-Xastir-2.0.8".

Doing this appears to be using a bit of the Github API that is not well 
documented in their release documentation.

For the few of you package maintainers who have already adjusted your package
build scripts to deal with the quirks of the technique I sent a couple of days
ago, "Thank you." But also, "Sorry, you have to do it again."  The 2.1.0 
release (which will now be delayed at least a couple more days while I fix all 
the documentation I just edited on Thursday night) will use the 
"Release-2.1.0" tag and not the "Xastir-Release-2.1.0" tag, the URL to use 
will be:

https://github.com/Xastir/Xastir/archive/Release-2.1.0/Xastir-Release-2.1.0.tar.
gz

and the thing will unpack without the double Xastir-.

-- 
Tom Russo    KM5VY
Tijeras, NM  

 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]