Ardour 5.0

[Robin Gareus]

tl;dr: We can't offer a better solution for the time being

On 08/28/2016 02:19 PM, Jaromír Mikeš wrote:
>>>
>>> ardour 5.1 is out ... I still don't have a idea how get a tarball :(

And 5.3 will be out later today :)

https://community.ardour.org/srctar is a direct link to the latest
upstream source of released version (currently still 5.1.0).

>> indeed the github download seems to be very broken.
>> it seems that this is intentional (at least that is how i interpret the
>> line `/* export-ignore` in .gitattributes¹).
>> i guess this is to force people to download via the ardour website².
>> ...

The motivation is different. As IOhannes already mentioned, Ardour
relies on `git describe` to work in order to extract the version.
Shallow git clones fail for the same reason.

One needs to run `./waf dist` on a full git clone in order to generate
libs/ardour/revision.cc prior to export. Github does not allow that.
GH does also not allow one to disable snapshots.

It was a very practical thing. After blacklisting the files, the
support-rate on #ardour IRC dropped significantly. I suppose most users
don't read the README, nor 'configure' output,  but they do understand
"empty zip". :)

If there's anything we can do to make debian packaging easier without
adding more 'newbie' support load on our end, I'll gladly do the
required changes.


The actual problem: We do not want to maintain version information in
multiple places. git tags are awesome.

Sadly gitattributes export-subst can only use information that is
available to git-log. One cannot currently walk the tree as git-describe
does.

Closest thing we've found is
http://stackoverflow.com/questions/19659976/add-tag-in-export-subst-file
but GH does not allow one to run arbitrary smudge filter commands either.

If you have a better solution, please don't hesitate to tell.

We're currently looking into getting `git describe` as supported feature
for export-subst upstream at git. But that's rather long term.

>> anyhow, i just fetched the upstream tarball and ran gbp-import-orig on it.
>> it should be possible (and possibly simple) to hack the d/watch to run
>> the actual download from the official download site, and use github only
>> as an announcement channel to check for new releases.

That sounds sensible to me, at least short/mid term. I suggest to add a
24h delay, though:

The git tag is the very first step in a release-cycle and as it happened
in the past (4.3, 4.5) and just now again with 5.2, the ensuing testing
after the tag may result in another version bump.

The "proper" way would be to parse the first <h1></h1> from
https://ardour.org/whatsnew.html That page is updated as last step every
release cycle.

If it helps I could set up a CGI script on ardour.org that is uscan
compatible. but I'll need some help to work around the missing
version-number in the upstream URL. Does uscan support Content-Disposition ?

ciao,
robin