[Slackbuilds-users] git clone instead of downloading a source tarball

[Willy Sudiarto Raharjo]

> Could I ask: Is it at all acceptable to submit an entry which does not
> download a source tarball but does a 'git clone' instead? Browsing
> through existing packages I could not find any which do this but it
> seems an obvious way to keep an entry up-to-date without maintainer
> updates to the Slackbuild script, albeit at a higher risk of future
> changes to the source breaking the build ?

No
We prefer a released tarball

If upstream doesn't release any tarball, the maintainer must make one by
cloning the repository at some point and host it somewhere public.



-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190201/617016e8/attachment.asc>