libvdpau-va-gl release tarball name

[bdubbs]

Right now the release tarball name is v0.3.4.tar.gz. A more descriptive name would be libvdpau-va-gl-0.3.4.tar.gz. Is this possible?

[i-rinat]

When I run command

wget --content-disposition 'https://codeload.github.com/i-rinat/libvdpau-va-gl/tar.gz/v0.3.4'

it downloads file named libvdpau-va-gl-0.3.4.tar.gz. Is that what you want?

[bdubbs]

Not really. We need a direct url without switches. See http://www.linuxfromscratch.org/blfs/view/svn/x/x7driver.html#libvdpau. We have about 800 packages that can be downloaded and do not want to have to ask users to use a special switch for just one package.

I'll also note that --content-disposition for wget is marked as experimental.

[i-rinat]

I have a dilemma. On github one doesn't upload a tarball, it's generated from tag instead. So to make URL contain libvdpau-va-gl-0.3.4.tar.gz at the end, I need to make tag named libvdpau-va-gl-0.3.4. I don't like duplication, but that's not the worst part. The worst part is that when one downloads file from browser, it's saved under different name, project name is prepended. So it will be something like libvdpau-va-gl-libvdpau-va-gl-0.3.4.tar.gz.

I'll also note that --content-disposition for wget is marked as experimental.

Yes, but most browsers honor 'Content-Disposition' header.

[pprkut]

Github does support release tarballs, although I'm not entirely sure how. As an example you can take a look at https://github.com/sampsyo/beets/releases/tag/v1.3.8 which is a tagged release. It offers a v1.3.8.zip and v1.3.8.tar.gz download, but also a beets-1.3.8.tar.gz one, which is what would be requested.

[bdubbs]

Interesting. I wonder how other packages do it? See for instance:

https://github.com/libass/libass/releases/ and https://github.com/fontforge/fontforge/releases/

In any case, I suppose we can work around the issue, but it's certainly not optimal.

We really have two issues. The first is for our book to tell users where to get the tarballs. Most use wget or curl rather than a browser. The second issue is that we have a set of scripts that check daily for new releases. Figuring that out for github in general requires customization for each package. Much better is the way it's done for gnu, kernel, kde, etc packages where they just give a directory listing of released packages.

[i-rinat]

I wonder how other packages do it?

I think they attach manually uploaded files. I've just did so for 0.3.4.

[bdubbs]

Thank you. That's perfect.

[i-rinat]

I'll try to keep uploading separate tarball for each new release.

[bdubbs]

Thanks again. For my releases, I have a checklist and some scripts that I use to make sure I do everything needed.