Skip to content

rust: fixups for publishing to crates.io - v3 #13005

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 4 commits into from

Conversation

jasonish
Copy link
Member

  • suricatactl: add description to Cargo.toml
  • htp: rename to suricata-htp, htp already taken
  • htp: remove authors field (deprecated)
  • htp: fix repository URL
  • Copy Cargo.lock to Cargo.lock.in

The version updates the Cargo.lock.

Additionally, always update the Cargo.lock.in to keep it in sync with
Cargo.lock. This will always make us aware when it has changed and needs to be
committed.

On a normal project where the Cargo.lock is checked in, it would be
normal to see an updated Cargo.lock in git status and the like. As we
use autoconf to generate this file, we should just copy it back to the
input file so we get the same convenience of seeing when it is
updated, which usually means it needs to be checked in.

However, to satisfy "make distcheck", only copy it if the input
template exists, if the input template does not exist we are in an out
of tree build.
For publishing to crates.io.
As the "suricata" crate depends on htp, we need to publish htp to
crates.io first, however "htp" name is already taken. So rename "htp" to
"suricata-htp".
Remove the authors field as it is deprecated.

Update the repository page to the Suricata repository.

Remove the homepage, it can be found via the reposistory page.
@victorjulien victorjulien added this to the 8.0 milestone Apr 11, 2025
@victorjulien
Copy link
Member

Merged in #13016, thanks!

@catenacyber
Copy link
Contributor

Thanks Jason, it works catenacyber/suricata-zabbix@cbcab95

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants