Doc updates for 4.1 release.

Author: brotskydotcom

CHANGELOG.md

@@ -1 +1,15 @@
-The detailed list of changes in each release can be found at https://github.com/hwchen/secret-service-rs/releases.
+## v4.1.0
+- expose dbus::Path fields on Items and Collections
+- allow creation of Items and Collections from a remembered path
+- update the MSRV to 1.78 (minimum for `Cargo.lock` version 4)
+- make lifetimes explicit to avoid Clippy complaints
+
+### v4.0.3
+- doc updates only (no code changes)
+
+### v4.0.2 API and doc fixes
+- add `Sync` to the error API
+- fix repository URL in `Cargo.toml`
+
+# v4.0.0 first public release
+- same API as v4 of the secret-service crate.

README.md

@@ -5,55 +5,37 @@
 [![crates.io](https://img.shields.io/crates/v/dbus-secret-service.svg?style=flat-square)](https://crates.io/crates/dbus-secret-service)
 [![docs.rs](https://docs.rs/dbus-secret-service/badge.svg)](https://docs.rs/dbus-secret-service)
 
-This crate is a knock-off of the [hwchen/secret-service](https://crates.io/crates/secret-service) crate, which is
-currently at version 4 and uses [zbus](https://crates.io/crates/zbus) to access the secret service. The basic
-collection, item and search APIs in this crate are meant to work the same as the blocking APIs in the zbus-based crate.
-If they don't, please file a bug.
+This crate started as a knock-off of the [secret-service](https://crates.io/crates/secret-service) crate, which uses [zbus](https://crates.io/crates/zbus) to access the secret service. The basic collection, item and search APIs in this crate are meant to work the same as the blocking APIs in the zbus-based crate. If they don't, please file a bug.
 
-Why do a knock-off? So that folks who write synchronous Rust apps that access the secret service (typically through
-the [hwchen/keyring](https://crates.io/crates/keyring) crate) are not required to add an async runtime. Because this
-knock-off uses lib-dbus, it doesn't require an async runtime.
-
-Why is this crate starting at version 4? Since its API matches a particular version of the dbus-based crate, I figured
-it would be clearest if its version number matched that version as well.
+Why do a knock-off? So that folks who write synchronous Rust apps that access the secret service (for example, [Keyring](https://open-source-cooperative/keyring-rs/wiki/Keyring) clients) are not required to add an async runtime. Because this knock-off uses lib-dbus, it doesn't require an async runtime.
 
 ## Usage
 
-For code usage examples, see the [documentation](https://docs.rs/dbus-secret-service).
+For code usage examples, see the [documentation](https://docs.rs/dbus-secret-service) and the [example program](https://github.com/open-source-cooperative/dbus-secret-service/blob/main/examples/example.rs).
 
-This crate has no default features, and requires no features to run. If you need your secrets to be encrypted on their
-way to and from the secret service, then add one of the crypto features:
+This crate has no default features, and requires no features to run. If you want your secrets to be encrypted on their
+way to and from the secret service (highly recommended), then add one of the crypto features:
 
 * `crypto-rust` uses pure Rust crates for encryption.
 * `crypto-openssl` uses the openssl libraries for encryption (which must be installed).
 
-See the [documentation](https://docs.rs/dbus-secret-service) for details on how to specify use of an encrypted session.
+See the [documentation](https://docs.rs/dbus-secret-service) for details on how to connect to the Secret Service with an encrypted session.
 
-To _build_ a project that uses this crate, your development machine will need
-to have the dbus development headers installed,
-and the openssl development headers for the `crypto-openssl` feature.
-To _run_ an application that uses this crate,
-your machine will need to have `libdbus` installed
-(almost all do),
-and the openssl libraries for the `crypto-openssl` feature.
-If you want to avoid this runtime requirement,
-you can specify the `vendored` feature at build time:
-this will statically link the needed libraries with your executable.
+To _build_ a project that uses this crate, your development machine will need to have the dbus development headers installed, and the openssl development headers for the `crypto-openssl` feature. To _run_ an application that uses this crate, your machine will need to have `libdbus` installed (almost all do), and the openssl libraries for the `crypto-openssl` feature. If you want to avoid this runtime requirement on clients, you can specify the `vendored` feature at build time: this will build and statically link the needed libraries with your executable.
 
 ### Functionality
 
-- SecretService: initialize dbus, create plain/encrypted session.
-- Collections: create, delete, search.
-- Items: create, delete, search, get/set secret.
+* SecretService: initialize dbus, create plain or encrypted session connection.
+* Collections: create, delete, search.
+* Items: create, delete, search, get/set secret.
 
-## Changelog
+## Change History
 
-v4.0.0: first release, same API as secret-service v4.0.
+See [CHANGELOG.md](CHANGELOG.md).
 
 ## License
 
-The copyright to all material in this repository belongs to the collective
-of contributors who have checked material into this repository.
+The copyright to all material in this repository belongs to the collective of contributors who have checked material into this repository.
 
 All material is this repository is licensed under either of
 
@@ -64,8 +46,4 @@ at your option.
 
 ## Contribution
 
-Unless you explicitly state otherwise,
-any contribution intentionally submitted for inclusion in the work by you,
-as defined in the Apache-2.0 license,
-shall be dual licensed as above,
-without any additional terms or conditions.
+Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.