Maybe it's time the community stepped in an provided alternative solutions to nixpkgs. We can talk about them here, but in the end somebody has to implement them.

[–] into_highest_invite@lemmygrad.ml 2 points 1 day ago* (last edited 1 day ago) (1 children)

no shallow is --shallow. the difference is --depth refers to the history (as reported by, e.g. git log), whereas shallow will only check out the root of the repository and any paths explicitly specified. i guess the article is describing some sort of problem with users who convert their shallow repository to a regular full repo. i wouldn't know a lot about that.

[–] onlinepersona@programming.dev 2 points 13 hours ago (1 children)

This is the documentation from git clone --help

--depth=<depth>

Create a shallow clone with a history truncated to the specified number of commits. Implies --single-branch unless --no-single-branch is given to fetch the histories near the tips of all branches. If you want to clone submodules shallowly, also pass --shallow-submodules.

[–] into_highest_invite@lemmygrad.ml 1 points 8 hours ago

oh that's my fault. i confused shallow with sparse (--sparse). my bad.