From: Erik Schilling <erik.schilling@linaro.org>
To: Linux-GPIO <linux-gpio@vger.kernel.org>
Cc: "Kent Gibson" <warthog618@gmail.com>,
"Bartosz Golaszewski" <bartosz.golaszewski@linaro.org>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Erik Schilling" <erik.schilling@linaro.org>
Subject: [PATCH libgpiod 1/3] bindings: rust: add version number to dependencies
Date: Mon, 12 Jun 2023 13:14:48 +0200 [thread overview]
Message-ID: <20230612-crates_io_publish-v1-1-70988ee9a655@linaro.org> (raw)
In-Reply-To: <20230612-crates_io_publish-v1-0-70988ee9a655@linaro.org>
When publishing to crates.io, all dependencies need to have a version
number. When building from crates.io the version number will be used,
otherwise the `path` is effective for builds when checking out the
repository.
As discussed on the maillinglist [1], each crate will have their own
version number (like the other language bindings) that will be bumped as
needed to fulfill the Rust SemVer requirements.
[1] https://lore.kernel.org/r/CACMJSes5+vT=NBqSe7xpSEPAEMmkgrZvJ8iKx7oBCKZQaGB_rg@mail.gmail.com/
Signed-off-by: Erik Schilling <erik.schilling@linaro.org>
---
bindings/rust/libgpiod/Cargo.toml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/bindings/rust/libgpiod/Cargo.toml b/bindings/rust/libgpiod/Cargo.toml
index 48681de..b19e888 100644
--- a/bindings/rust/libgpiod/Cargo.toml
+++ b/bindings/rust/libgpiod/Cargo.toml
@@ -18,7 +18,7 @@ edition = "2021"
errno = "0.2.8"
intmap = "2.0.0"
libc = "0.2.39"
-libgpiod-sys = { path = "../libgpiod-sys" }
+libgpiod-sys = { version = "0.1", path = "../libgpiod-sys" }
thiserror = "1.0"
[dev-dependencies]
--
2.40.1
next prev parent reply other threads:[~2023-06-12 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 11:14 [PATCH libgpiod 0/3] bindings: rust: prepare for crates.io publish Erik Schilling
2023-06-12 11:14 ` Erik Schilling [this message]
2023-06-12 11:14 ` [PATCH libgpiod 2/3] bindings: rust: exclude Makefile.am from package Erik Schilling
2023-06-12 11:14 ` [PATCH libgpiod 3/3] bindings: rust: document build without install Erik Schilling
2023-06-13 3:56 ` [PATCH libgpiod 0/3] bindings: rust: prepare for crates.io publish Viresh Kumar
2023-06-13 8:16 ` Bartosz Golaszewski
2023-06-13 10:37 ` Erik Schilling
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=20230612-crates_io_publish-v1-1-70988ee9a655@linaro.org \
--to=erik.schilling@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=bartosz.golaszewski@linaro.org \
--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).