From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libprelude/
Date: Mon, 7 Dec 2020 23:44:52 +0000 (UTC) [thread overview]
Message-ID: <1607384681.349072e067b616f34fe15d4705769879dacd57c1.marecki@gentoo> (raw)
commit: 349072e067b616f34fe15d4705769879dacd57c1
Author: Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Mon Dec 7 23:12:11 2020 +0000
Commit: Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Mon Dec 7 23:44:41 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=349072e0
dev-libs/libprelude-5.2.0-r10: use LUA_DEPS in BDEPEND as well
Safer that way, using two different Lua implementations at build time
and at run time can sometimes result in subtle problems that are a major
pain in the neck to debug.
Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>
dev-libs/libprelude/libprelude-5.2.0-r10.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/libprelude/libprelude-5.2.0-r10.ebuild b/dev-libs/libprelude/libprelude-5.2.0-r10.ebuild
index 5f21c422533..501ea6e31ee 100644
--- a/dev-libs/libprelude/libprelude-5.2.0-r10.ebuild
+++ b/dev-libs/libprelude/libprelude-5.2.0-r10.ebuild
@@ -34,7 +34,7 @@ DEPEND="${RDEPEND}"
BDEPEND=">=dev-lang/swig-4.0.0
dev-util/gtk-doc-am
sys-devel/flex
- lua? ( dev-lang/lua:* )
+ lua? ( ${LUA_DEPS} )
perl? ( dev-lang/perl:= virtual/perl-ExtUtils-MakeMaker )
python? ( ${PYTHON_DEPS} )
ruby? ( ${RUBY_DEPS} )
next reply other threads:[~2020-12-07 23:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 23:44 Marek Szuba [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-30 12:11 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libprelude/ Arthur Zamarin
2021-03-09 12:44 Joonas Niilola
2021-01-01 0:35 Michał Górny
2020-10-12 12:39 Joonas Niilola
2020-06-13 6:25 Hans de Graaff
2020-04-16 6:51 Joonas Niilola
2020-02-11 12:16 Michał Górny
2019-04-08 17:43 Hans de Graaff
2018-07-18 7:32 Tony Vroon
2018-04-13 10:11 Hans de Graaff
2017-09-08 7:56 Michał Górny
2017-08-05 18:49 Hans de Graaff
2017-03-07 20:30 Göktürk Yüksek
2016-12-06 17:48 Göktürk Yüksek
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=1607384681.349072e067b616f34fe15d4705769879dacd57c1.marecki@gentoo \
--to=marecki@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