public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Lucio Sauer" <watermanpaint@posteo.net>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: x11-misc/i3status-rust/
Date: Sun, 10 Nov 2024 22:27:15 +0000 (UTC)	[thread overview]
Message-ID: <1731277519.32cd7459f36dca8c41754c27f0430158fc9f31e9.watermanpaint@gentoo> (raw)

commit:     32cd7459f36dca8c41754c27f0430158fc9f31e9
Author:     Lucio Sauer <watermanpaint <AT> posteo <DOT> net>
AuthorDate: Sun Nov 10 22:25:19 2024 +0000
Commit:     Lucio Sauer <watermanpaint <AT> posteo <DOT> net>
CommitDate: Sun Nov 10 22:25:19 2024 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=32cd7459

x11-misc/i3status-rust: replace dependency on virtual/rust

Signed-off-by: Lucio Sauer <watermanpaint <AT> posteo.net>

 .../{i3status-rust-0.33.1.ebuild => i3status-rust-0.33.1-r1.ebuild}   | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/x11-misc/i3status-rust/i3status-rust-0.33.1.ebuild b/x11-misc/i3status-rust/i3status-rust-0.33.1-r1.ebuild
similarity index 99%
rename from x11-misc/i3status-rust/i3status-rust-0.33.1.ebuild
rename to x11-misc/i3status-rust/i3status-rust-0.33.1-r1.ebuild
index 45393e950..6e00995fc 100644
--- a/x11-misc/i3status-rust/i3status-rust-0.33.1.ebuild
+++ b/x11-misc/i3status-rust/i3status-rust-0.33.1-r1.ebuild
@@ -374,7 +374,8 @@ CRATES="
 	zvariant_derive@4.0.2
 	zvariant_utils@1.1.0
 "
-inherit cargo optfeature
+RUST_MIN_VER="1.76.0"
+inherit cargo optfeature rust
 
 DESCRIPTION="A feature-rich and resource-friendly replacement for i3status, written in Rust."
 HOMEPAGE="https://github.com/greshake/i3status-rust/"
@@ -403,7 +404,6 @@ DEPEND="dev-libs/openssl:=
 RDEPEND="${DEPEND}"
 BDEPEND="
 	virtual/pkgconfig
-	>=virtual/rust-1.76.0
 	pipewire? ( sys-devel/clang )
 "
 


             reply	other threads:[~2024-11-10 22:27 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-10 22:27 Lucio Sauer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-13 14:11 [gentoo-commits] repo/proj/guru:dev commit in: x11-misc/i3status-rust/ Lucio Sauer
2025-01-13 14:11 Lucio Sauer
2024-07-11 11:08 Lucio Sauer
2024-04-29 14:14 Lucio Sauer
2024-04-29 14:14 Lucio Sauer
2024-02-20  1:17 Lucio Sauer
2023-11-26 23:49 Lucio Sauer
2023-11-26 23:49 Lucio Sauer
2023-09-12 20:33 Lucio Sauer
2023-09-12 20:33 Lucio Sauer
2023-09-02 20:07 Lucio Sauer
2023-09-02 20:07 Lucio Sauer
2023-08-02  9:36 Lucio Sauer
2023-08-02  9:36 Lucio Sauer
2023-07-28 18:19 Lucio Sauer
2023-07-28 18:19 Lucio Sauer
2023-07-04 21:47 Lucio Sauer
2023-07-02 12:11 Lucio Sauer
2023-06-29  0:02 Lucio Sauer
2023-06-14 10:06 Lucio Sauer
2023-06-14 10:06 Lucio Sauer
2023-06-02  0:40 Lucio Sauer
2023-06-02  0:40 Lucio Sauer
2023-05-19 15:13 Lucio Sauer
2023-04-13 15:43 Lucio Sauer
2023-03-25  3:46 Lucio Sauer
2023-03-25  3:46 Lucio Sauer
2023-03-20  6:13 Lucio Sauer
2023-03-20  6:13 Lucio Sauer
2023-02-19 11:28 Joe Kappus
2022-05-14 16:45 Jose Storopoli
2021-12-15 11:23 Andrew Ammerlaan
2021-03-28 11:43 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2021-03-28 11:14 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-08-30 18:27 Philip DeMonaco

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=1731277519.32cd7459f36dca8c41754c27f0430158fc9f31e9.watermanpaint@gentoo \
    --to=watermanpaint@posteo.net \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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