From: Erik Schilling <erik.schilling@linaro.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
Linux-GPIO <linux-gpio@vger.kernel.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Manos Pitsidianakis <manos.pitsidianakis@linaro.org>,
Kent Gibson <warthog618@gmail.com>,
Erik Schilling <erik.schilling@linaro.org>
Subject: [libgpiod][PATCH 0/2] bindings: rust: feature gate unreleased features
Date: Fri, 06 Oct 2023 09:24:25 +0200 [thread overview]
Message-ID: <20231006-b4-bindings-old-version-fix-v1-0-a65f431afb97@linaro.org> (raw)
When releasing the 0.2.0 version of the libgpiod crate, I did not
realize that there were C lib features that were not released yet.
Helpfully, vhost-device's CI went up in flames and revealed this [1].
This suggests a way to handle that and sketches how further updates can
be handled.
I acknowledge that this may be very strange to C developers...
Traditionally, one would just use whatever your distro provided and the
distro would make sure that dependencies update in lock-step.
However, in Rust the default way to consume libraries is to pull them
from crates.io. This is a balancing act for -sys crates which link to
distro-provided libraries on the system. Since crates.io does not wait
for distros to update their libraries, crates will need to support a
wider range of system libraries.
This sets up / sketches the infrastructure for that.
Only the first commit is intended to be merged. The second one just
sketches how a release will look like once it happens.
[1] https://buildkite.com/rust-vmm/vhost-device-ci/builds/1746#018b0110-b9d3-468a-973c-c3bbc27cd479
To: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linux-GPIO <linux-gpio@vger.kernel.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
Cc: Kent Gibson <warthog618@gmail.com>
Signed-off-by: Erik Schilling <erik.schilling@linaro.org>
---
Erik Schilling (2):
bindings: rust: feature gate unreleased features
DONOTMERGE: bindings: rust: simulate v2.1 release
bindings/rust/libgpiod-sys/Cargo.toml | 9 +++++++--
bindings/rust/libgpiod/Cargo.toml | 4 ++++
bindings/rust/libgpiod/Makefile.am | 2 +-
bindings/rust/libgpiod/README.md | 14 ++++++++++++++
bindings/rust/libgpiod/src/line_request.rs | 2 ++
bindings/rust/libgpiod/tests/line_request.rs | 1 +
6 files changed, 29 insertions(+), 3 deletions(-)
---
base-commit: e7b02c2259d97c77107c77b68e3bc1664e6703c1
change-id: 20231006-b4-bindings-old-version-fix-789973703b77
Best regards,
--
Erik Schilling <erik.schilling@linaro.org>
next reply other threads:[~2023-10-06 7:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 7:24 Erik Schilling [this message]
2023-10-06 7:24 ` [libgpiod][PATCH 1/2] bindings: rust: feature gate unreleased features Erik Schilling
2023-10-06 9:25 ` Viresh Kumar
2023-10-06 7:24 ` [libgpiod][PATCH 2/2] DONOTMERGE: bindings: rust: simulate v2.1 release Erik Schilling
2023-10-09 8:58 ` [libgpiod][PATCH 0/2] bindings: rust: feature gate unreleased features Bartosz Golaszewski
2023-10-09 11:38 ` Erik Schilling
2023-10-09 12:43 ` Bartosz Golaszewski
2023-10-09 14:16 ` Erik Schilling
2023-10-09 14:32 ` Bartosz Golaszewski
2023-10-09 14:39 ` Manos Pitsidianakis
2023-10-09 15:21 ` Erik Schilling
2023-10-10 6:55 ` Bartosz Golaszewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231006-b4-bindings-old-version-fix-v1-0-a65f431afb97@linaro.org \
--to=erik.schilling@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linux-gpio@vger.kernel.org \
--cc=manos.pitsidianakis@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=warthog618@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).