You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know how to clone the git repository recursively in order to checkout all gitmodules but for packaging purposes (I am packaging/porting the FreeBSD version) that is not very convenient.
Could you please create source tarballs that contain all gitmodules? Before you mention the assets that allow to download a .tar.gz, those don't contain the gitmodules:
Providing a tarball that contains all the submodules has the following advantages for packager:
tarball contains all submodules
at the exact version it was released (not just a lose branch; yes submodules have the capability to use tags but this project doesn't do that)
packaging frameworks can use simple, single fetch (fetch, wget) to get the entire source code
Thank you for your consideration.
The text was updated successfully, but these errors were encountered:
I could prolly write another CI job for this so it's done automatically on the next release. Would that be fine or do you require a source tarball on the latest release as well?
I could create a tarball for this release and self-host it.
I have re-tagged a v0.5.0 on my fork with #450 cherry-picked and uploaded the source tarball from that to our v0.5.0 release. I hope this helps with your packaging effort.
Requested Feature
I know how to clone the git repository recursively in order to checkout all gitmodules but for packaging purposes (I am packaging/porting the FreeBSD version) that is not very convenient.
Could you please create source tarballs that contain all gitmodules? Before you mention the assets that allow to download a
.tar.gz
, those don't contain the gitmodules:Providing a tarball that contains all the submodules has the following advantages for packager:
Thank you for your consideration.
The text was updated successfully, but these errors were encountered: