create source tarball with a script

[dvzrv]

create_assets.sh: Adding script to create assets (including any submodules) as .tar.gz in the form rack-<tag>.tar.gz in the same folder the script is residing in.

Additionally, it can be used to create a detached PGP signature of the created source tarball.

E.g. to create the source tarball for tag v1.0.0:

./create_assets.sh -v v1.0.0

To create the source tarball for tag v1.0.0 and an additional detached PGP signature, where <e-mail> is the mail address you have created a PGP key for:

./create_assets.sh -v v1.0.0 -s <e-mail>

Fixes #1396.

[AndrewBelt]

This looks nice, but since I don't need this (but you do), would you mind keeping it in your fork and pulling/merging whenever you need to update?

[dvzrv]

I'm sorry, but I don't have the time to do that. I maintain over 300 packages.

I don't quite understand your chain of thought: Under what circumstances would you not be interested in having reproducible and verifiable sources for others, guaranteeing a flowing back of information about the build system and the components?
This is not only making my life easier, but basically that of every packager or $person building rack from source.

[AndrewBelt]

No worries, I'll merge this if customers start requesting it. Currently it seems they're happy using the official builds, which have the additional advantage of VCV providing professional support for.

[dvzrv]

No worries, I'll merge this if customers start requesting it.

What classifies as a customer though? How many more than two users on github requesting it would be required?

Currently it seems they're happy using the official builds, which have the additional advantage of VCV providing professional support for.

That might be. However, there literally are no other builds available (or packages for that matter) that they could even choose from (software on Linux is usually installed via package managers).

[falkTX]

I think kxstudio users would be quite happy to have this packaged properly in the repos.
Should I tell them to voice their opinion here?

[dvzrv]

The same goes for Arch Linux/ Manjaro/ Parabola, etc. users.

[trebmuh]

LibraZiK users would welcome having Rack nicely and properly packaged in the users repository too.

[diovudau]

Your userbase might be windows, by the sheer numbers alone, but your power-user and open source-base is linux. Making sure building and packaging can be done properly is a high priority for every project.

[eeickmeyer]

Leader of Ubuntu Studio here. Arguably, Ubuntu Studio is the largest, most widely used multimedia creation operating system on the planet. I was actually looking at packaging this and getting it included in the Ubuntu repositories and then included in Ubuntu Studio by default, but I can't do that unless there's a proper source tarball.

So, that's a +1 from me. Doing this would get your software in front of users and recording studios worldwide that don't run (and don't want to run) Windows.

[AndrewBelt]

Moving to #1396 as an implementation of this should be in Makefiles, not a script.