vasm-legacy: Use tagged releases when packaging

There will soon be changes to vasm-legacy's default branch ("publish") which you won't want to follow immediately. The git clone should be removed from the SlackBuild. I have created the tag vasm-legacy-2.7.53, which is just a copy of publish as it was when the package was last built.

Attached is a SlackBuild with the needed change done. Thought that might be simpler and clearer than producing a patch for it. VERSION and BUILDNUM have not been incremented, as the build itself will be identical. For now, leave the scripts in var/vabs/vasm-legacy/src/sbin -- I didn't edit out their use yet. But be advised that they will be replaced by symlinks or scripts in future versions.

Please use only tagged, announced versions for future packages. Or clone elsewhere, or replace entirely.

Comments (2)