From: "Andreas Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-libs/libnsl/
Date: Mon, 30 Apr 2018 11:26:50 +0000 (UTC) [thread overview]
Message-ID: <1525087515.71627502e290946938c5ae9bdecd910b14447a4b.dilfridge@gentoo> (raw)
commit: 71627502e290946938c5ae9bdecd910b14447a4b
Author: Mike Gilbert <floppym <AT> gentoo <DOT> org>
AuthorDate: Tue Jan 2 01:37:37 2018 +0000
Commit: Andreas Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Mon Apr 30 11:25:15 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=71627502
net-libs/libnsl: inherit multilib-build in the dummy ebuild
This populates IUSE with the appropriate flags.
We don't actually want to RDEPEND on sys-libs/glibc[multilib] since the
multilib USE flag is forced on/off by the user's profile, and a mismatch
would just cause confusion.
[Sorry for the delay -dilfridge]
Closes: https://bugs.gentoo.org/643058
net-libs/libnsl/{libnsl-0.ebuild => libnsl-0-r1.ebuild} | 3 +++
1 file changed, 3 insertions(+)
diff --git a/net-libs/libnsl/libnsl-0.ebuild b/net-libs/libnsl/libnsl-0-r1.ebuild
similarity index 88%
rename from net-libs/libnsl/libnsl-0.ebuild
rename to net-libs/libnsl/libnsl-0-r1.ebuild
index eeebf1d587c..cf2e1bea64a 100644
--- a/net-libs/libnsl/libnsl-0.ebuild
+++ b/net-libs/libnsl/libnsl-0-r1.ebuild
@@ -3,6 +3,9 @@
EAPI=6
+# Used only to populate IUSE, bug 643058
+inherit multilib-build
+
DESCRIPTION="Public client interface for NIS(YP) and NIS+ in a IPv6 ready version"
HOMEPAGE="https://github.com/thkukuk/libnsl"
next reply other threads:[~2018-04-30 11:26 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 11:26 Andreas Hüttel [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-23 4:17 [gentoo-commits] repo/gentoo:master commit in: net-libs/libnsl/ Ionen Wolkens
2023-12-15 13:21 Arthur Zamarin
2023-12-15 10:53 Arthur Zamarin
2023-12-15 10:38 Arthur Zamarin
2023-12-15 7:49 Sam James
2023-12-15 7:14 Sam James
2023-12-15 7:14 Sam James
2023-12-15 7:14 Sam James
2023-10-13 15:00 Sam James
2023-08-20 20:28 Andreas K. Hüttel
2022-10-29 12:08 Sam James
2022-06-14 8:15 Jakov Smolić
2022-06-14 8:15 Jakov Smolić
2022-06-14 6:39 Jakov Smolić
2022-06-14 6:18 Jakov Smolić
2022-06-14 5:54 Jakov Smolić
2022-06-13 21:50 Jakov Smolić
2022-06-13 21:50 Jakov Smolić
2022-06-13 21:13 Sam James
2021-09-19 1:00 Sam James
2021-08-18 8:04 Lars Wendler
2021-08-14 3:48 Sam James
2021-05-24 15:09 Mike Gilbert
2020-09-12 9:00 Sergei Trofimovich
2020-08-31 0:42 Sam James
2020-08-17 0:20 Robin H. Johnson
2020-08-11 19:11 Sergei Trofimovich
2020-08-11 16:18 Sam James
2020-08-11 14:23 Agostino Sarubbo
2020-08-11 14:13 Agostino Sarubbo
2020-08-10 19:25 Sergei Trofimovich
2020-08-10 12:04 Agostino Sarubbo
2020-08-10 9:30 Agostino Sarubbo
2020-07-11 12:58 Sergei Trofimovich
2020-07-08 22:34 Lars Wendler
2020-07-06 18:21 Lars Wendler
2020-03-23 23:58 Sergei Trofimovich
2019-05-04 19:40 Andreas K. Hüttel
2018-11-14 16:22 Robin H. Johnson
2018-09-05 19:31 Anthony G. Basile
2018-09-05 15:36 Anthony G. Basile
2018-08-26 8:10 Jeroen Roovers
2018-07-02 18:27 Markus Meier
2018-06-25 16:06 Tobias Klausmann
2018-06-23 8:24 Sergei Trofimovich
2018-06-06 15:25 Thomas Deutschmann
2018-06-05 17:51 Mike Frysinger
2018-06-05 17:25 Mart Raudsepp
2018-06-02 21:48 Sergei Trofimovich
2018-06-02 19:28 Andreas Hüttel
2018-01-22 16:19 Michael Haubenwallner
2018-01-12 4:10 Mike Frysinger
2017-11-23 20:48 Thomas Deutschmann
2017-11-21 19:13 Mike Gilbert
2017-11-21 19:11 Mike Gilbert
2017-11-21 19:11 Mike Gilbert
2017-11-12 14:16 Andreas Hüttel
2017-11-06 0:43 Anthony G. Basile
2017-11-01 11:48 Andreas Hüttel
2017-10-28 18:56 Andreas Hüttel
2017-10-28 18:28 Andreas Hüttel
2017-09-18 11:50 Michael Haubenwallner
2017-09-16 17:25 Sergei Trofimovich
2017-09-16 15:48 Andreas Hüttel
2017-09-07 20:29 Andreas Hüttel
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=1525087515.71627502e290946938c5ae9bdecd910b14447a4b.dilfridge@gentoo \
--to=dilfridge@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