public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-libs/nlopt/
Date: Sat, 28 Sep 2024 14:43:39 +0000 (UTC)	[thread overview]
Message-ID: <1727534586.bf702b6cee0133e094b50378336326b6bff4926b.sam@gentoo> (raw)

commit:     bf702b6cee0133e094b50378336326b6bff4926b
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Sep 28 14:41:53 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Sep 28 14:43:06 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bf702b6c

sci-libs/nlopt: fix pkg_setup w/ USE=-guile

Like in 20c679298cd29c57dba3dce93339b0a1780284e5. This seems to be
the only other such case in-tree.

Note that fortran-2_pkg_setup is fine to call unconditionally
because it checks itself if it should be used if FORTRAN_OPTIONAL is set.

Bug: https://bugs.gentoo.org/940441
Fixes: 01f1676c357e17cfde5abb0ccca96766e69bbe6f
Signed-off-by: Sam James <sam <AT> gentoo.org>

 sci-libs/nlopt/nlopt-2.7.1-r100.ebuild | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/sci-libs/nlopt/nlopt-2.7.1-r100.ebuild b/sci-libs/nlopt/nlopt-2.7.1-r100.ebuild
index 55bc5573894b..385cdb5a674d 100644
--- a/sci-libs/nlopt/nlopt-2.7.1-r100.ebuild
+++ b/sci-libs/nlopt/nlopt-2.7.1-r100.ebuild
@@ -31,6 +31,11 @@ RDEPEND="
 DEPEND="${RDEPEND}"
 BDEPEND="python? ( dev-lang/swig )"
 
+pkg_setup() {
+	use guile && guile-single_pkg_setup
+	fortran-2_pkg_setup
+}
+
 src_prepare() {
 	cmake_src_prepare
 


             reply	other threads:[~2024-09-28 14:43 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-28 14:43 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-08 10:59 [gentoo-commits] repo/gentoo:master commit in: sci-libs/nlopt/ Sam James
2024-11-08  3:54 Sam James
2024-06-04 20:21 Andrew Ammerlaan
2024-04-08 18:50 Andrew Ammerlaan
2024-03-02 14:55 Arthur Zamarin
2024-01-11  9:38 Sam James
2024-01-10 12:31 Jakov Smolić
2024-01-10 12:10 Sam James
2023-03-19  3:22 Sam James
2023-03-07 11:42 Sam James
2023-03-04  7:37 Arthur Zamarin
2023-02-24 11:24 Andrew Ammerlaan
2022-09-12 20:31 Michael Orlitzky
2022-09-12 20:31 Michael Orlitzky
2022-07-22  7:49 Agostino Sarubbo
2022-07-22  7:43 Agostino Sarubbo
2022-07-18 20:07 Sam James
2022-07-09 12:17 Agostino Sarubbo
2022-07-09 12:14 Agostino Sarubbo
2022-05-18  1:36 Michael Orlitzky
2021-10-25 17:20 Arthur Zamarin
2020-12-14  0:46 Sam James
2020-07-21  9:42 Andreas Sturmlechner
2020-07-21  9:33 Agostino Sarubbo
2020-07-21  8:48 Agostino Sarubbo
2020-06-22  1:41 Mark Wright
2020-06-21 14:11 Mark Wright
2020-06-21 14:11 Mark Wright
2020-06-21  4:54 Mark Wright
2020-01-22 21:50 Michał Górny
2020-01-16  7:03 Michał Górny
2017-04-20 16:41 David Seifert
2016-12-20 16:52 Tobias Klausmann

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=1727534586.bf702b6cee0133e094b50378336326b6bff4926b.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