From: "Gilles Dartiguelongue" <eva@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gnome:master commit in: sci-geosciences/geocode-glib/
Date: Sat,  1 Dec 2018 17:41:34 +0000 (UTC)	[thread overview]
Message-ID: <1543686089.6444288f48dbeb3b986e20ca3a0f4fd834b6b59f.eva@gentoo> (raw)
commit:     6444288f48dbeb3b986e20ca3a0f4fd834b6b59f
Author:     Gilles Dartiguelongue <eva <AT> gentoo <DOT> org>
AuthorDate: Sat Dec  1 17:40:07 2018 +0000
Commit:     Gilles Dartiguelongue <eva <AT> gentoo <DOT> org>
CommitDate: Sat Dec  1 17:41:29 2018 +0000
URL:        https://gitweb.gentoo.org/proj/gnome.git/commit/?id=6444288f
sci-geosciences/geocode-glib: use gtk-doc instead of doc USE flag
As discussed on gentoo-dev mailing list, this is now the standard for
gtk-doc documentation.
Message-ID: <1535141206.6451.19.camel <AT> gentoo.org>
Subject: [gentoo-dev] [RFC] New global USE flag: gtk-doc
Package-Manager: Portage-2.3.52, Repoman-2.3.12
Manifest-Sign-Key: 0x5A56C8CD0C13248A
Signed-off-by: Gilles Dartiguelongue <eva <AT> gentoo.org>
 sci-geosciences/geocode-glib/geocode-glib-3.26.0-r1.ebuild | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/sci-geosciences/geocode-glib/geocode-glib-3.26.0-r1.ebuild b/sci-geosciences/geocode-glib/geocode-glib-3.26.0-r1.ebuild
index 192e56f0..1503d5d1 100644
--- a/sci-geosciences/geocode-glib/geocode-glib-3.26.0-r1.ebuild
+++ b/sci-geosciences/geocode-glib/geocode-glib-3.26.0-r1.ebuild
@@ -10,7 +10,7 @@ HOMEPAGE="https://git.gnome.org/browse/geocode-glib"
 LICENSE="LGPL-2"
 SLOT="0"
 KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~ia64 ~ppc ~ppc64 ~sparc ~x86"
-IUSE="+introspection test"
+IUSE="gtk-doc +introspection test"
 
 RDEPEND="
 	>=dev-libs/glib-2.44:2
@@ -20,9 +20,9 @@ RDEPEND="
 	introspection? ( >=dev-libs/gobject-introspection-0.6.3:= )
 "
 DEPEND="${RDEPEND}
-	dev-util/gtk-doc
 	>=sys-devel/gettext-0.19.6
 	virtual/pkgconfig
+	gtk-doc? ( dev-util/gtk-doc )
 	test? ( sys-apps/dbus )
 "
 
@@ -34,8 +34,8 @@ src_configure() {
 	local emesonargs=(
 		$(meson_use test enable-installed-tests)
 		$(meson_use introspection enable-introspection)
-		"-Denable-gtk-doc=true"
-		)
+		$(meson_use gtk-doc enable-gtk-doc)
+	)
 	meson_src_configure
 }
 
next             reply	other threads:[~2018-12-01 17:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-01 17:41 Gilles Dartiguelongue [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-02-23 20:37 [gentoo-commits] proj/gnome:master commit in: sci-geosciences/geocode-glib/ Mart Raudsepp
2018-10-11 17:48 Sobhan Mohammadpour
2018-09-10 21:33 Gilles Dartiguelongue
2018-06-24 12:14 Sobhan Mohammadpour
2018-02-06 15:53 Sobhan Mohammadpour
2015-05-17 15:39 Gilles Dartiguelongue
2015-05-12 22:20 Gilles Dartiguelongue
2015-05-08 23:36 Gilles Dartiguelongue
2014-12-26 21:53 Gilles Dartiguelongue
2014-10-11 16:43 Gilles Dartiguelongue
2014-04-15 22:05 Gilles Dartiguelongue
2014-02-12 23:48 Gilles Dartiguelongue
2013-12-02 23:46 Gilles Dartiguelongue
2013-11-16 14:53 Gilles Dartiguelongue
2013-11-13 13:15 Priit Laes
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=1543686089.6444288f48dbeb3b986e20ca3a0f4fd834b6b59f.eva@gentoo \
    --to=eva@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