From f2f7b6ffec7bf657966353c850d25c6ab218ff7c Mon Sep 17 00:00:00 2001 From: Vika Date: Tue, 22 Oct 2024 21:52:10 +0300 Subject: vendor libsecret The libsecret-rs crate is unmaintained, so I'm vendoring it for now. Bumping the glib version turned out to be enough. The exact process I used was: 1. Cloning the repository 2. Making changes 3. `cargo build` to ensure it works 4. `cargo package --no-verify` (b/c it tries to build all crates separately instead of the entire workspace as a whole) 5. `mkdir libsecret/sys -p` 6. `tar --strip-components 1 -C libsecret -xvf ../libsecret-rs/target/package/libsecret-0.6.0.crate` 7. `tar --strip-components 1 -C libsecret/sys -xvf ../libsecret-rs/target/package/libsecret-sys-0.6.0.crate` Then `Cargo.toml` is modified to ensure the libsecret and its `-sys` crate build out of my vendored sources. In the future, if I gain maintainership of the `libsecret` crate, I could just revert this commit to make it point back to the upstream. --- libsecret/sys/README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 libsecret/sys/README.md (limited to 'libsecret/sys/README.md') diff --git a/libsecret/sys/README.md b/libsecret/sys/README.md new file mode 100644 index 0000000..9a47559 --- /dev/null +++ b/libsecret/sys/README.md @@ -0,0 +1,10 @@ +# libsecret-rs + +The Rust bindings of [libsecret](https://gitlab.gnome.org/GNOME/libsecret). + +- Website: + +# Documentation + +- libsecret: +- libsecret_sys: -- cgit 1.4.1