From: "Zac Medico" <zmedico@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: virtual/podofo-build/
Date: Sun, 21 May 2017 22:58:04 +0000 (UTC) [thread overview]
Message-ID: <1495407481.957a06fa8f4a58066925f78c75290670c2841e07.zmedico@gentoo> (raw)
commit: 957a06fa8f4a58066925f78c75290670c2841e07
Author: Zac Medico <zmedico <AT> gentoo <DOT> org>
AuthorDate: Sun May 21 22:38:22 2017 +0000
Commit: Zac Medico <zmedico <AT> gentoo <DOT> org>
CommitDate: Sun May 21 22:58:01 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=957a06fa
virtual/podofo-build: add tools USE flag (bug 608876)
Package-Manager: Portage-2.3.6, Repoman-2.3.2
virtual/podofo-build/metadata.xml | 3 +++
virtual/podofo-build/podofo-build-0.9.6_pre20170508-r1.ebuild | 4 ++--
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/virtual/podofo-build/metadata.xml b/virtual/podofo-build/metadata.xml
index 05aee7d1995..3b38cb243ae 100644
--- a/virtual/podofo-build/metadata.xml
+++ b/virtual/podofo-build/metadata.xml
@@ -4,5 +4,8 @@
<maintainer type="person"><email>zmedico@gentoo.org</email></maintainer>
<use>
<flag name="boost">Add support for boost</flag>
+ <flag name="tools">
+ Build and install commandline tools.
+ </flag>
</use>
</pkgmetadata>
diff --git a/virtual/podofo-build/podofo-build-0.9.6_pre20170508-r1.ebuild b/virtual/podofo-build/podofo-build-0.9.6_pre20170508-r1.ebuild
index 87ad18211e3..a8ba84f9f2e 100644
--- a/virtual/podofo-build/podofo-build-0.9.6_pre20170508-r1.ebuild
+++ b/virtual/podofo-build/podofo-build-0.9.6_pre20170508-r1.ebuild
@@ -6,10 +6,10 @@ EAPI=6
DESCRIPTION="Virtual package for building against PoDoFo"
SLOT="0/${PVR}"
KEYWORDS="amd64 ~arm hppa ppc ppc64 ~sparc x86"
-IUSE="+boost idn debug test"
+IUSE="+boost idn debug test +tools"
# Pull in boost for build-against header dependency (see bug #503802).
RDEPEND="
- app-text/podofo:0/${PVR}[boost=,idn=,debug=,test=]
+ app-text/podofo:0/${PVR}[boost=,idn=,debug=,test=,tools=]
boost? ( dev-libs/boost )
"
next reply other threads:[~2017-05-21 22:58 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 22:58 Zac Medico [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-25 2:43 [gentoo-commits] repo/gentoo:master commit in: virtual/podofo-build/ Zac Medico
2023-09-22 8:37 Joonas Niilola
2023-09-21 6:17 Zac Medico
2023-01-22 6:38 Sam James
2023-01-22 6:38 Sam James
2023-01-22 6:38 Sam James
2023-01-22 6:38 Sam James
2022-12-26 17:55 Zac Medico
2022-07-15 9:09 Sam James
2022-02-26 19:52 Zac Medico
2021-05-13 15:19 David Seifert
2021-01-09 10:36 Sam James
2020-07-28 21:25 Sergei Trofimovich
2020-06-06 0:51 Zac Medico
2019-06-28 20:49 Sergei Trofimovich
2019-05-20 10:58 Mikle Kolyada
2019-05-19 13:14 Thomas Deutschmann
2019-05-12 22:03 Sergei Trofimovich
2018-07-26 17:21 Zac Medico
2017-11-23 20:50 Zac Medico
2017-11-14 2:04 Zac Medico
2017-07-03 23:17 Zac Medico
2017-05-18 6:43 Zac Medico
2017-05-18 5:01 Michael Weber
2017-05-16 13:05 Agostino Sarubbo
2017-05-16 8:01 Agostino Sarubbo
2017-05-16 5:00 Jeroen Roovers
2017-05-15 14:17 Agostino Sarubbo
2017-05-12 10:06 Zac Medico
2017-05-12 10:02 Zac Medico
2017-05-12 9:56 Zac Medico
2017-05-10 20:07 Zac Medico
2017-05-01 19:09 Zac Medico
2017-02-07 17:39 Zac Medico
2016-07-25 6:19 Zac Medico
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=1495407481.957a06fa8f4a58066925f78c75290670c2841e07.zmedico@gentoo \
--to=zmedico@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