You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This tool appears to fail if the homepage field is not specified in Cargo.toml. C-METADATA, which is linked in the README, states that homepage is optional and further states:
The homepage metadata should only be set if there is a unique website for the crate other than the source repository or API documentation. Do not make homepage redundant with either the documentation or repository values. For example, serde sets homepage to https://serde.rs, a dedicated website.
Given that a lot of crates these days will just have a repository URL and not a separate homepage, I think it would be good to make homepage optional in cargo-aur (following the approach in C-METADATA). The url field in the PKGBUILD could be set to homepage or, if that is not present, documentation or, if that is not present, repository (the last being a required field per C-METADATA).
Happy to work on a PR for this if helpful.
The text was updated successfully, but these errors were encountered:
This tool appears to fail if the
homepage
field is not specified inCargo.toml
. C-METADATA, which is linked in the README, states thathomepage
is optional and further states:Given that a lot of crates these days will just have a repository URL and not a separate homepage, I think it would be good to make
homepage
optional incargo-aur
(following the approach in C-METADATA). Theurl
field in the PKGBUILD could be set tohomepage
or, if that is not present,documentation
or, if that is not present,repository
(the last being a required field per C-METADATA).Happy to work on a PR for this if helpful.
The text was updated successfully, but these errors were encountered: