public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Patrice Clement" <monsieurp@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: www-apache/mod_security/
Date: Sun, 10 Mar 2019 22:38:36 +0000 (UTC)	[thread overview]
Message-ID: <1552257330.61c02bdcbe2db4c25cb2d76291794a649a4c1ba2.monsieurp@gentoo> (raw)

commit:     61c02bdcbe2db4c25cb2d76291794a649a4c1ba2
Author:     Tomas Mozes <hydrapolic <AT> gmail <DOT> com>
AuthorDate: Fri Mar  8 09:35:32 2019 +0000
Commit:     Patrice Clement <monsieurp <AT> gentoo <DOT> org>
CommitDate: Sun Mar 10 22:35:30 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=61c02bdc

www-apache/mod_security: fix building USE=doc.

Patch-by: Dennis Lichtenthäler
Closes: https://bugs.gentoo.org/679522
Package-Manager: Portage-2.3.62, Repoman-2.3.12
Signed-off-by: Tomáš Mózes <hydrapolic <AT> gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/11296
Signed-off-by: Patrice Clement <monsieurp <AT> gentoo.org>

 www-apache/mod_security/mod_security-2.9.3.ebuild | 9 ++-------
 1 file changed, 2 insertions(+), 7 deletions(-)

diff --git a/www-apache/mod_security/mod_security-2.9.3.ebuild b/www-apache/mod_security/mod_security-2.9.3.ebuild
index 41cfb5afbc1..f04a0e597d6 100644
--- a/www-apache/mod_security/mod_security-2.9.3.ebuild
+++ b/www-apache/mod_security/mod_security-2.9.3.ebuild
@@ -60,19 +60,14 @@ src_configure() {
 		$(use_enable mlogc)
 		$(use_with lua)
 		$(use_enable lua lua-cache)
-		$(use_enable jit pcre-jit) )
+		$(use_enable jit pcre-jit)
+		$(use_enable doc docs) )
 
 	econf ${myconf[@]}
 }
 
 src_compile() {
 	default
-
-	# Building the docs is broken at the moment, see e.g.
-	# https://github.com/SpiderLabs/ModSecurity/issues/1322
-	if use doc; then
-		doxygen doc/doxygen-apache.conf || die 'failed to build documentation'
-	fi
 }
 
 src_install() {


             reply	other threads:[~2019-03-10 22:38 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-10 22:38 Patrice Clement [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-08 14:51 [gentoo-commits] repo/gentoo:master commit in: www-apache/mod_security/ Jakov Smolić
2025-03-08 12:10 Sam James
2024-12-01 12:12 Sam James
2024-01-11 14:06 Joonas Niilola
2023-03-09 23:34 Sam James
2023-03-09 23:34 Sam James
2023-02-05  9:12 Joonas Niilola
2023-02-05  9:12 Joonas Niilola
2022-12-02 17:19 John Helmert III
2022-12-02  3:38 Sam James
2022-12-02  3:34 Sam James
2022-11-19  3:23 Sam James
2022-02-20  0:31 Sam James
2022-02-20  0:31 Sam James
2021-12-22  0:45 Sam James
2021-12-22  0:44 Sam James
2021-12-21  2:05 Sam James
2021-06-01 20:18 Sam James
2021-01-25 17:38 Marek Szuba
2021-01-23  4:20 Sam James
2021-01-23  4:09 Sam James
2020-11-09 18:36 Marek Szuba
2019-03-04  1:35 Thomas Deutschmann
2018-10-31 18:34 Pacho Ramos
2018-10-20 18:00 Mikle Kolyada
2018-10-14  1:44 Thomas Deutschmann
2016-08-07  9:30 Pacho Ramos
2016-07-17 23:12 Aaron Bauman
2016-07-17 22:16 Aaron Bauman
2016-07-08 10:02 Agostino Sarubbo
2016-07-08  7:53 Agostino Sarubbo
2016-06-27  8:48 Agostino Sarubbo
2016-06-27  8:23 Agostino Sarubbo

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=1552257330.61c02bdcbe2db4c25cb2d76291794a649a4c1ba2.monsieurp@gentoo \
    --to=monsieurp@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