From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/eza/
Date: Mon, 4 Mar 2024 06:00:03 +0000 (UTC) [thread overview]
Message-ID: <1709531729.7bbe8523321447cd14ac683242a8d253fb629c07.sam@gentoo> (raw)
commit: 7bbe8523321447cd14ac683242a8d253fb629c07
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Mar 4 05:54:09 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Mar 4 05:55:29 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7bbe8523
sys-apps/eza: update environment variable for forcing system libgit2
See d98b521e041fe26b4f5e7b495e1cf11b7963903a.
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-apps/eza/{eza-0.17.2.ebuild => eza-0.17.2-r1.ebuild} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sys-apps/eza/eza-0.17.2.ebuild b/sys-apps/eza/eza-0.17.2-r1.ebuild
similarity index 98%
rename from sys-apps/eza/eza-0.17.2.ebuild
rename to sys-apps/eza/eza-0.17.2-r1.ebuild
index f31a0687ecba..ce4507d1c264 100644
--- a/sys-apps/eza/eza-0.17.2.ebuild
+++ b/sys-apps/eza/eza-0.17.2-r1.ebuild
@@ -208,7 +208,7 @@ SLOT="0"
KEYWORDS="~amd64 ~arm64 ~loong ~ppc64 ~riscv ~x86"
IUSE="+git"
-DEPEND="git? ( dev-libs/libgit2:= )"
+DEPEND="git? ( >=dev-libs/libgit2-1.7.0:= )"
RDEPEND="${DEPEND}"
BDEPEND=">=virtual/rust-1.70.0"
@@ -229,7 +229,7 @@ src_configure() {
local myfeatures=(
$(usev git)
)
- export LIBGIT2_SYS_USE_PKG_CONFIG=1
+ export LIBGIT2_NO_VENDOR=1
export PKG_CONFIG_ALLOW_CROSS=1
cargo_src_configure --no-default-features
}
next reply other threads:[~2024-03-04 6:00 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 6:00 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-27 19:48 [gentoo-commits] repo/gentoo:master commit in: sys-apps/eza/ Yixun Lan
2024-09-27 19:48 Yixun Lan
2024-09-09 11:51 Yixun Lan
2024-08-21 7:51 Joonas Niilola
2024-08-21 7:51 Joonas Niilola
2024-07-07 2:05 Sam James
2024-07-07 2:05 Sam James
2024-07-04 3:22 Sam James
2024-07-04 1:18 Sam James
2024-06-06 6:47 Sam James
2024-06-06 6:17 Joonas Niilola
2024-06-05 20:10 Arthur Zamarin
2024-04-30 6:42 Sam James
2024-03-21 7:24 Ionen Wolkens
2024-03-11 10:50 Petr Vaněk
2024-03-09 11:03 Jakov Smolić
2024-03-09 6:47 Joonas Niilola
2024-03-08 23:58 Sam James
2024-03-02 10:06 Arthur Zamarin
2024-01-28 17:34 Matt Turner
2024-01-21 4:02 Sam James
2024-01-16 8:39 Florian Schmaus
2024-01-16 8:39 Florian Schmaus
2024-01-16 8:39 Florian Schmaus
2024-01-13 13:09 Florian Schmaus
2023-12-17 6:20 Arthur Zamarin
2023-12-08 6:46 Joonas Niilola
2023-12-08 6:46 Joonas Niilola
2023-11-30 2:08 Sam James
2023-11-13 6:44 Sam James
2023-10-27 7:11 Florian Schmaus
2023-10-25 16:57 Jakov Smolić
2023-10-20 9:14 Florian Schmaus
2023-10-12 18:03 Florian Schmaus
2023-10-12 18:03 Florian Schmaus
2023-10-12 18:03 Florian Schmaus
2023-10-12 5:54 WANG Xuerui
2023-10-09 10:54 Florian Schmaus
2023-10-09 10:54 Florian Schmaus
2023-10-03 23:38 Sam James
2023-09-28 5:22 Joonas Niilola
2023-09-27 2:55 Sam James
2023-09-27 2:55 Sam James
2023-09-23 9:50 Sam James
2023-09-15 6:15 Sam James
2023-09-13 2:15 Sam James
2023-09-11 19:57 Florian Schmaus
2023-09-11 11:41 Arthur Zamarin
2023-09-11 0:39 Sam James
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=1709531729.7bbe8523321447cd14ac683242a8d253fb629c07.sam@gentoo \
--to=sam@gentoo.org \
--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