diff options
| author | Aleksana <me@aleksana.moe> | 2024-07-16 03:55:51 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-07-15 22:55:51 +0300 |
| commit | d582f13e5e6f68b6207a5ad8ba3a3ade470fefae (patch) | |
| tree | b53f2ce7b157d07b65b7d5105b804181bef8431f /pkgs/development/python-modules/rangehttpserver | |
| parent | 23a62d05e269bf5363205aef91f95cb857b2b01e (diff) | |
treewide: switch to cargoHash (#327127)
* nickel: switch to cargoHash
* gnvim-unwrapped: switch to cargoHash
* surrealdb-migrations: switch to cargoHash
* wluma: switch to cargoHash
* httm: switch to cargoHash
No need (observed) for these packages to have a vendor Cargo.lock. If they for some reason have to use a different Cargo.lock than upstream, they should copy that to the build directory as well, otherwise the build will fail. They don't, so I infer there's no reason to use Cargo.lock.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions