crate.io data access policy (user agent)
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | fetch2/wget: allow identifying with a bitbake user agentlib/ | +18 | 0 replies | |
| 2/2 | fetch2/crate: identify as bitbake to crates.iolib/ | +17 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] crate.io data access policy (user agent)
These patches addresses the part about setting an application specific user agent when making API calls to crates.io:
https://crates.io/data-access#api
I'm a little bit hesitant on the first patch, as that changes how checkstatus identifies slightly by adding contact information. Another option would be to leave it intact except for the crate fetcher. But I feel this is introducing more complexity in favor of, quite possibly excessive, defensiveness.
A third option is to leave out the contact information altogether and just use bitbake/<version> since the request about contact information is only "strongly suggested".
Johan Anderholm (2):
fetch2/wget: allow identifying with a bitbake user agent fetch2/crate: identify as bitbake to crates.io
lib/bb/fetch2/crate.py | 18 +++++++++++++++++- lib/bb/fetch2/wget.py | 19 ++++++++++++++++++- 2 files changed, 35 insertions(+), 2 deletions(-)
Signature · 1 line
2.34.1