Release source tarball
nunotexbsd opened this issue · comments
Hello,
Could this project provide a release source tarball, e.g, heimer-3.4.0.tar.gz to be included toguether with Release Assets?
This have the advantage to download source code from a fixed tarball instead of an auto-generated one: https://github.com/juzzlin/Heimer/archive/refs/tags/3.4.0.tar.gz.
Since I'm maintaining FreeBSD Heimer port, instead of using github account name/project to get auto-generated source tarball, I could simply use a simple command to fetch from a static url:
from:
PORTNAME= heimer
DISTVERSION= 3.4.0
USE_GITHUB= yes
GH_ACCOUNT= juzzlin
GH_PROJECT= Heimer
distinfo:
SHA256 (juzzlin-Heimer-3.4.0_GH0.tar.gz) = ###
SIZE (juzzlin-Heimer-3.4.0_GH0.tar.gz) = ###
to:
PORTNAME= heimer
DISTVERSION= 3.4.0
MASTER_SITES= https://github.com/juzzlin/Heimer/releases/download/${DISTVERSION}/
distinfo:
SHA256 (heimer-3.4.0.tar.gz) = ###
SIZE (heimer-3.4.0.tar.gz) = ###
IMO, all packaging systems that needs fetching and compiling from source will beneficit with this static tarball.
Thanks,
Nuno Eduardo Teixeira
eduardo@FreeBSD.org
Sure it's possible. I had to read this 10 times until I realized that the auto-generated download link indeed differs from the actual file name. Didn't know that :)
Nice to hear that. I'm doing this "campaign" alone with all github projects connected to ports that I maintain and it's not an easy task to explain the difference of a static tarball and a auto-generated one and, the access to both by aumotated packaging systems like FreeBSD ports, e.g.. I'm using a very simple example to explain this difference:
https://github.com/jordansissel/xdotool/releases
Cheers
Fixed in b8acac9.
From now on I will release also heimer-x.y.z.tar.gz.
Thank you!
Cheers