From: "orbea" <orbea@riseup.net>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/libressl:master commit in: dev-lang/rust/
Date: Tue, 25 Apr 2023 01:29:55 +0000 (UTC) [thread overview]
Message-ID: <1682384292.bf02b61806f155e14b489a5367c16d13619e861a.orbea@gentoo> (raw)
commit: bf02b61806f155e14b489a5367c16d13619e861a
Author: orbea <orbea <AT> riseup <DOT> net>
AuthorDate: Tue Apr 25 00:58:12 2023 +0000
Commit: orbea <orbea <AT> riseup <DOT> net>
CommitDate: Tue Apr 25 00:58:12 2023 +0000
URL: https://gitweb.gentoo.org/repo/proj/libressl.git/commit/?id=bf02b618
dev-lang/rust: add 1.69.0-r1, drop 1.69.0
Signed-off-by: orbea <orbea <AT> riseup.net>
dev-lang/rust/{rust-1.69.0.ebuild => rust-1.69.0-r1.ebuild} | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/dev-lang/rust/rust-1.69.0.ebuild b/dev-lang/rust/rust-1.69.0-r1.ebuild
similarity index 99%
rename from dev-lang/rust/rust-1.69.0.ebuild
rename to dev-lang/rust/rust-1.69.0-r1.ebuild
index 2987458..8b3df2a 100644
--- a/dev-lang/rust/rust-1.69.0.ebuild
+++ b/dev-lang/rust/rust-1.69.0-r1.ebuild
@@ -320,12 +320,13 @@ src_configure() {
fi
rust_targets="${rust_targets#,}"
- local tools='"cargo"'
+ # cargo and rustdoc are mandatory and should always be included
+ local tools='"cargo","rustdoc"'
use clippy && tools+=',"clippy"'
use miri && tools+=',"miri"'
use profiler && tools+=',"rust-demangler"'
use rustfmt && tools+=',"rustfmt"'
- use rust-analyzer && tools+=',"rust-analyzer","analysis"'
+ use rust-analyzer && tools+=',"rust-analyzer"'
use rust-src && tools+=',"src"'
local rust_stage0_root
next reply other threads:[~2023-04-25 1:29 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 1:29 orbea [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-09 17:02 [gentoo-commits] repo/proj/libressl:master commit in: dev-lang/rust/ orbea
2024-11-09 17:02 orbea
2024-10-22 16:44 orbea
2024-10-18 15:17 orbea
2024-09-18 16:28 orbea
2024-09-18 16:28 orbea
2024-08-27 19:35 orbea
2024-08-14 15:40 orbea
2024-07-24 18:56 orbea
2024-05-31 0:59 orbea
2024-05-03 1:06 orbea
2024-04-22 23:44 orbea
2024-04-05 17:24 orbea
2024-04-02 18:50 orbea
2024-03-24 15:22 orbea
2024-03-24 15:22 orbea
2024-03-11 14:57 orbea
2024-03-10 8:30 orbea
2024-02-16 15:06 orbea
2024-02-16 15:06 orbea
2024-01-31 0:07 orbea
2024-01-16 21:14 orbea
2024-01-14 15:06 orbea
2024-01-14 15:06 orbea
2023-12-23 20:16 orbea
2023-12-22 14:56 orbea
2023-12-12 19:49 orbea
2023-11-14 17:45 orbea
2023-11-05 3:44 orbea
2023-10-18 17:01 orbea
2023-10-15 22:19 orbea
2023-10-09 17:14 orbea
2023-09-29 19:19 orbea
2023-09-17 16:22 orbea
2023-09-17 16:22 orbea
2023-08-29 21:11 orbea
2023-08-06 21:40 orbea
2023-07-20 19:07 orbea
2023-06-28 1:12 orbea
2023-06-14 14:41 orbea
2023-06-09 16:23 orbea
2023-06-08 18:29 orbea
2023-06-05 0:17 orbea
2023-04-21 3:48 orbea
2023-04-06 21:31 Quentin Retornaz
2023-03-28 18:51 Quentin Retornaz
2023-01-31 23:14 Quentin Retornaz
2023-01-17 0:52 Quentin Retornaz
2023-01-14 23:23 Quentin Retornaz
2022-12-21 20:26 Quentin Retornaz
2022-11-15 21:18 Quentin Retornaz
2022-09-29 22:58 Quentin Retornaz
2022-09-24 20:10 Quentin Retornaz
2022-09-24 20:10 Quentin Retornaz
2022-09-23 16:00 Quentin Retornaz
2022-07-23 21:19 Quentin Retornaz
2022-07-04 16:49 Quentin Retornaz
2022-07-04 16:49 Quentin Retornaz
2022-06-10 23:36 Quentin Retornaz
2022-06-02 1:44 Quentin Retornaz
2022-04-28 23:40 Quentin Retornaz
2022-04-28 23:40 Quentin Retornaz
2022-01-21 21:26 Quentin Retornaz
2022-01-15 19:13 Quentin Retornaz
2021-11-06 18:17 Quentin Retornaz
2021-11-06 18:17 Quentin Retornaz
2021-07-28 21:05 Quentin Retornaz
2021-06-16 15:49 Quentin Retornaz
2021-06-16 15:49 Quentin Retornaz
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=1682384292.bf02b61806f155e14b489a5367c16d13619e861a.orbea@gentoo \
--to=orbea@riseup.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