From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-misc/weggli/
Date: Wed, 12 Jul 2023 06:36:00 +0000 (UTC) [thread overview]
Message-ID: <1689143589.cbce8be942bf4255e243fdffdc80e5b51c24eb57.sam@gentoo> (raw)
commit: cbce8be942bf4255e243fdffdc80e5b51c24eb57
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Jul 12 06:32:54 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Jul 12 06:33:09 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cbce8be9
app-misc/weggli: drop redundant filter-lto
After dc51935f7aae5f89d1ffecabef322680979952b8, cargo.eclass filters for us.
I don't plan on doing all of these, just ones where I've either touched the pkg
before or I can clearly see it was 'just the normal case'.
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-misc/weggli/weggli-0.2.4.ebuild | 9 +--------
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/app-misc/weggli/weggli-0.2.4.ebuild b/app-misc/weggli/weggli-0.2.4.ebuild
index bad640d606b9..f4580b114190 100644
--- a/app-misc/weggli/weggli-0.2.4.ebuild
+++ b/app-misc/weggli/weggli-0.2.4.ebuild
@@ -125,7 +125,7 @@ CRATES="
# tree-sitter grammar. Patching the .so to need the system's
# libtree-sitter-cpp seems to work, but it is not correct because the
# weggli grammar has some minor modifications.
-inherit cargo flag-o-matic
+inherit cargo
DESCRIPTION="a fast and robust semantic search tool for C and C++ codebases"
HOMEPAGE="https://github.com/googleprojectzero/weggli"
@@ -139,10 +139,3 @@ SLOT="0"
KEYWORDS="~amd64 ~arm64"
QA_FLAGS_IGNORED="usr/bin/${PN}"
-
-src_prepare() {
- default
-
- # 854741
- filter-lto
-}
next reply other threads:[~2023-07-12 6:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 6:36 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-25 22:16 [gentoo-commits] repo/gentoo:master commit in: app-misc/weggli/ Sam James
2022-08-12 17:57 Matthew Smith
2022-08-12 17:57 Matthew Smith
2022-04-13 9:37 Matthew Smith
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=1689143589.cbce8be942bf4255e243fdffdc80e5b51c24eb57.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