[Slackbuilds-users] Request for shallow Git clone support over HTTPS

[Nicholas Hubbard]

> git clone --depth=1 git://git.slackbuilds.org/slackbuilds.git it 
> works just fine 

Thank you very much for the responses!

That URL does support shallow cloning. However, Git’s native 
git://
transport provides neither encryption nor server 
authentication. Since
the package manager downloads build scripts that are executed as
root, I’d prefer to retain HTTPS.

Matteo’s suggestion of using an HTTPS mirror makes sense, and I’ll
probably use that if enabling smart HTTP isn’t practical.

My preference would still be for my package manager's default 
configuration
to point directly to git.slackbuilds.org, while retaining 
HTTPS. Are there
hosting or maintenance considerations that would make enabling 
smart HTTP
undesirable?
-- 
Nicholas B. Hubbard
Keys: https://github.com/NicholasBHubbard/public-keys
Key ID: 1B047444A3CDC5320D33F5187319CE683E94B9B0
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 264 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20260912/a4934693/attachment.asc>