add sparse url in cargo package guide #26937
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GiteaBot
added
the
lgtm/need 2
merlleu
changed the title
|
Could you write an additional sentence what's the difference? |
|
Yep, Sparse replaces the cloning of the repo by simple http requests to each file supposed to be in the repo. It's faster and on gitea it's using directly packages api instead of the cargo-index repo, so this means we can remove some complexity from the cargo index integration:
https://blog.rust-lang.org/inside-rust/2023/01/30/cargo-sparse-protocol.html |
|
Sry, not to me, into the docs 😄 I know what it is, I implemented it 😏 |
lunny
approved these changes
Sep 6, 2023
GiteaBot
added
lgtm/need 1
wxiaoguang
approved these changes
Sep 13, 2023
GiteaBot
added
lgtm/done
lunny
added
the
reviewed/wait-merge
GiteaBot
removed
the
reviewed/wait-merge
zjjhot
added a commit
to zjjhot/gitea
that referenced
this pull request
Sep 13, 2023
* giteaofficial/main: fix media description render for orgmode (go-gitea#26895) Show OpenID Connect and OAuth on signup page (go-gitea#20242) Update status and code index after changing the default branch (go-gitea#27018) add sparse url in cargo package guide (go-gitea#26937) Add missing 404 response to Swagger (go-gitea#27038) Fix object storage path handling (go-gitea#27024) [skip ci] Updated translations via Crowdin bump rootful to 16gb setup go in the nightly release pipeline Speed up nightly builds (go-gitea#27045) Improve repo/user/org search (go-gitea#27030) Use Actuated.dev runner for nightly builds update snap package (go-gitea#27021) resolve issue with sort icons on admin/users and admin/runners (go-gitea#24360)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
The current package guide for cargo gives you only the git index, with the HTTP Index stabilized being used as default for crates.io and being better for most use-cases.
However, it's not documented that gitea supports the sparse spec, and it does not require the _crates-index git repo for the sparse api.
I personally think we should push users to use the sparse instead of the git repository. (Even let users disable crates-index repos if they only want to use sparse)