public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/source-highlight/
Date: Fri, 29 Nov 2019 20:37:20 +0000 (UTC)	[thread overview]
Message-ID: <1575059833.a350c472095e13c1ca27a7b04d601a0fdb13101e.slyfox@gentoo> (raw)

commit:     a350c472095e13c1ca27a7b04d601a0fdb13101e
Author:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Fri Nov 29 20:36:40 2019 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Fri Nov 29 20:37:13 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a350c472

dev-util/source-highlight: bump up tu 3.1.9

Closes: https://bugs.gentoo.org/683402
Package-Manager: Portage-2.3.79, Repoman-2.3.18
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>

 dev-util/source-highlight/Manifest                 |  1 +
 .../source-highlight/source-highlight-3.1.9.ebuild | 51 ++++++++++++++++++++++
 2 files changed, 52 insertions(+)

diff --git a/dev-util/source-highlight/Manifest b/dev-util/source-highlight/Manifest
index bdc185bc2be..659d0fb87a7 100644
--- a/dev-util/source-highlight/Manifest
+++ b/dev-util/source-highlight/Manifest
@@ -1 +1,2 @@
 DIST source-highlight-3.1.8.tar.gz 1648351 BLAKE2B 1ce1590c86f7aed9d27bb21bce6b0869828b28068d71404410e080b85f6354eb6f520cec8c81d1e9170dd90b158dc4536e5287a04bf2d271fa26354fb853ea32 SHA512 00a49ab180460750614b38be9a569478d1d34d01f601ebc7452a4fee8475a19faf9bb9fb2f256c6b40d43fbc3d34962a77ba8b9833483345c4e4a42faad6976c
+DIST source-highlight-3.1.9.tar.gz 1717234 BLAKE2B 6eb40b2274df0772c4a241504e5db5dfdaac600549e0b11aba726f7b4d5ab600c3849a8815bc782ad1bb1f99b69766527645dd202731bde4b2466c663842c47c SHA512 d8e154e9a5d62c77807e4e5d36c0faed5ce2964291be5f8b83e2968a6de52229503689a4ca2109a717ae2632a14b63ec937ca0430c91684c72063f6bc0294195

diff --git a/dev-util/source-highlight/source-highlight-3.1.9.ebuild b/dev-util/source-highlight/source-highlight-3.1.9.ebuild
new file mode 100644
index 00000000000..1b8ae59a6d7
--- /dev/null
+++ b/dev-util/source-highlight/source-highlight-3.1.9.ebuild
@@ -0,0 +1,51 @@
+# Copyright 1999-2019 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+inherit bash-completion-r1 flag-o-matic
+
+DESCRIPTION="Generate highlighted source code as an (x)html document"
+HOMEPAGE="https://www.gnu.org/software/src-highlite/source-highlight.html"
+SRC_URI="mirror://gnu/src-highlite/${P}.tar.gz"
+LICENSE="GPL-3"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x86-macos ~sparc-solaris"
+SLOT="0"
+IUSE="doc static-libs"
+
+RDEPEND=">=dev-libs/boost-1.62.0:=[threads]
+	dev-util/ctags"
+DEPEND="${RDEPEND}"
+BDEPEND=""
+
+src_configure() {
+	# required as rev-dep of dev-libs/boost-1.62.0
+	# https://wiki.gentoo.org/wiki/Project:C%2B%2B/Maintaining_ABI
+	append-cxxflags -std=c++14
+
+	econf \
+		--with-boost="${EPREFIX}/usr" \
+		--with-boost-regex="boost_regex" \
+		--without-bash-completion \
+		$(use_enable static-libs static)
+}
+
+src_install () {
+	use doc && local HTML_DOCS=( doc/*.{html,css,java} )
+	default
+
+	# That's not how we want it
+	rm -rf "${ED%/}"/usr/share/{aclocal,doc} || die
+
+	# package provides .pc file
+	find "${D}" -name '*.la' -delete || die
+
+	dobashcomp completion/source-highlight
+}
+
+src_test() {
+	export LD_LIBRARY_PATH="${S}/lib/srchilite/.libs/"
+	# upstream uses the same temporary filenames in numerous places
+	# see https://bugs.gentoo.org/635100
+	emake -j1 check
+}


             reply	other threads:[~2019-11-29 20:37 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29 20:37 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-03  6:56 [gentoo-commits] repo/gentoo:master commit in: dev-util/source-highlight/ Sam James
2024-02-02 17:51 Arthur Zamarin
2024-02-02 14:46 Arthur Zamarin
2024-02-02  4:51 Sam James
2024-02-02  4:51 Sam James
2024-02-02  4:44 Sam James
2024-02-02  4:44 Sam James
2024-02-02  4:44 Sam James
2024-02-02  4:44 Sam James
2023-12-28  2:19 Sam James
2023-12-28  2:19 Sam James
2023-12-28  2:19 Sam James
2023-12-28  2:19 Sam James
2023-12-28  2:19 Sam James
2022-05-10  0:44 WANG Xuerui
2021-07-19 23:14 Marek Szuba
2021-01-06 22:55 Fabian Groffen
2020-07-25  9:18 Sergei Trofimovich
2020-07-18 18:09 Sam James
2020-06-28 20:44 Agostino Sarubbo
2020-06-28 20:37 Agostino Sarubbo
2020-06-28 20:33 Agostino Sarubbo
2020-06-28 20:30 Agostino Sarubbo
2020-06-25  7:00 Agostino Sarubbo
2020-06-24 17:22 Sergei Trofimovich
2020-06-22 18:23 Sergei Trofimovich
2020-03-23 23:58 Sergei Trofimovich
2019-11-29 23:12 Sergei Trofimovich
2019-11-29 23:03 Sergei Trofimovich
2019-11-29 20:50 Sergei Trofimovich
2019-11-18  2:18 Aaron Bauman
2019-04-17 20:01 Sergei Trofimovich
2019-04-13 13:57 Tiziano Müller
2019-04-09  9:48 Fabian Groffen
2018-05-13 10:44 Mart Raudsepp
2017-11-25 19:03 Sergei Trofimovich
2017-10-25 23:53 Manuel Rüger
2017-10-23 21:00 Sergei Trofimovich
2017-10-22 20:33 Thomas Deutschmann
2017-10-19  5:00 Markus Meier
2017-10-15 21:42 Sergei Trofimovich
2017-10-14 14:10 Sergei Trofimovich
2016-10-08 18:44 David Seifert

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=1575059833.a350c472095e13c1ca27a7b04d601a0fdb13101e.slyfox@gentoo \
    --to=slyfox@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