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

[Nicholas Hubbard]

Hello! I hope this is the correct list to post this on.

Would it be possible to enable shallow git clones over HTTPS for 
the SlackBuilds
repository?

I develop an SBo package manager, and recently added support for 
shallow clones since
it only needs the current contents of a branch. Avoiding the repos 
long history reduces
download sizes and disk usage.

However, currently this command:

  git clone --depth=1 https://git.slackbuilds.org/slackbuilds/
  
Fails with:

  fatal: dumb http transport does not support shallow capabilities

It looks like the HTTPS endpoint uses Git’s “dumb HTTP” 
transport. Would you consider
enabling read-only smart HTTP access, perhaps through Git’s 
git-http-backend? Smart
HTTP supports shallow clones, allowing clients to download a 
branch’s current contents
without its full history. My understanding is that smart HTTP can 
be enabled at the
existing URL while preserving support for older clients through 
the dumb HTTP transport.

Thanks for considering this and thanks for maintaining 
SlackBuilds.org!
-- 
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/20260911/f825aaf6/attachment.asc>