Perfect, that works for me.

I'll share what I've got for the benefit of anyone else since the curl result contains `next-YYYYMMDD` and the source tarball does not contain `next-` so it needs to be removed with another simple step in bash:

    ver_with_next=$(basename $(curl -Ls -o/dev/null -w '%{url_effective}' https://trac.chirp.danplanet.com/download?stream=next))
    ver_without_next=${ver_with_next//next-/}
    curl -o ./chirp-src.tar.gz https://trac.chirp.danplanet.com/chirp_next/${ver_with_next}/chirp-${ver_without_next}.tar.gz

Tony

January 27, 2023 at 10:52 PM, "Dan Smith via chirp_devel" <chirp_devel@intrepid.danplanet.com> wrote:

If there was a URL like `https://trac.chirp.danplanet.com/chirp_next/latest` which either contained simple text or redirected to "https://trac.chirp.danplanet.com/chirp_next/next-YYYYMMDD/chirp-next-YYYYMMDD.tar.gz" that would really help out, at least from what I've seen with snap, flatpak and appimage building thus far.

The link on the download page almost does this:

https://trac.chirp.danplanet.com/download?stream=next

and will redirect to the build dir. You could pull the build name out of the URL it sends you to:

$ curl -Ls -o/dev/null -w '%{url_effective}' https://trac.chirp.danplanet.com/download?stream=next
https://trac.chirp.danplanet.com/chirp_next/next-20230127/

$ basename $(curl -Ls -o/dev/null -w '%{url_effective}' https://trac.chirp.danplanet.com/download?stream=next)
next-20230127

--Dan
_______________________________________________
chirp_devel mailing list
chirp_devel@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers