From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/kramdown/
Date: Mon, 10 Dec 2018 07:33:04 +0000 (UTC) [thread overview]
Message-ID: <1544426624.7375b3c73ebc43278dd1ef5f90fbec15ee60cc9c.graaff@gentoo> (raw)
commit: 7375b3c73ebc43278dd1ef5f90fbec15ee60cc9c
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Mon Dec 10 07:23:44 2018 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Mon Dec 10 07:23:44 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7375b3c7
dev-ruby/kramdown: add 1.17.0
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
Package-Manager: Portage-2.3.51, Repoman-2.3.11
dev-ruby/kramdown/Manifest | 1 +
dev-ruby/kramdown/kramdown-1.17.0.ebuild | 55 ++++++++++++++++++++++++++++++++
2 files changed, 56 insertions(+)
diff --git a/dev-ruby/kramdown/Manifest b/dev-ruby/kramdown/Manifest
index 885ea2af430..68bab58c821 100644
--- a/dev-ruby/kramdown/Manifest
+++ b/dev-ruby/kramdown/Manifest
@@ -1,2 +1,3 @@
DIST kramdown-1.14.0.gem 250368 BLAKE2B 78d3638ec58a5c237a9350cad1edabf2d4fa0307013a0ced18f6835c4a8cdd623e4825b06670d5c588147013b191912f93e51e74ab1fe007761c117334f378aa SHA512 bd6295db2fe0d3a7dca936d47f0aaf7f939a86361dfdd3203a52683a9eb11a68075cad7d068cc56a315db3c14e73cf5aebb87531ba3086301a7521c5a86f9905
DIST kramdown-1.16.2.gem 258048 BLAKE2B a9b35b9e3882cafa32721d0555fa10d806973d4f6e7b617395c00acd3aee43552d74be2442411dc04fec48f7878a7459621ee7848365c165b51959e03a9451da SHA512 da6981969aca283c50b5a34650833c1364afcf74ecc64daba1eed20b198490bf1fdda91096f37574281b50f36713326c367307137446b1fd84a049358a13e4d7
+DIST kramdown-1.17.0.gem 260608 BLAKE2B 56f0abb2c94ab2de31bcd71940c22610efc8143c434295627513735b5983a369b0d9b36a88477a4e0b14bb23a3d314280702655c854cb7134e29bebc1f276966 SHA512 0f98f4234dec41b53d7f116be1075176c7fcbf21621c6f52a9e5b4055a777b01f1a0a912be81a651e85df022e7bab3ac183ee66cd87abeae092cd1920aceff04
diff --git a/dev-ruby/kramdown/kramdown-1.17.0.ebuild b/dev-ruby/kramdown/kramdown-1.17.0.ebuild
new file mode 100644
index 00000000000..375d01b07f8
--- /dev/null
+++ b/dev-ruby/kramdown/kramdown-1.17.0.ebuild
@@ -0,0 +1,55 @@
+# Copyright 1999-2018 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=6
+USE_RUBY="ruby23 ruby24"
+
+RUBY_FAKEGEM_EXTRADOC="README.md AUTHORS CONTRIBUTERS"
+
+RUBY_FAKEGEM_EXTRAINSTALL="data"
+
+inherit ruby-fakegem
+
+DESCRIPTION="Yet-another-markdown-parser but fast, pure Ruby, using strict syntax definition"
+HOMEPAGE="https://kramdown.gettalong.org/"
+
+LICENSE="MIT"
+
+SLOT="0"
+KEYWORDS="~amd64 ~arm ~arm64 ~ppc ~ppc64"
+IUSE="latex"
+
+LATEX_DEPS="latex? ( dev-texlive/texlive-latex dev-texlive/texlive-latexextra )"
+RDEPEND+=" ${LATEX_DEPS}"
+DEPEND+=" test? ( ${LATEX_DEPS} app-text/htmltidy )"
+
+ruby_add_rdepend "dev-ruby/prawn:2
+ >=dev-ruby/prawn-table-0.2.2 =dev-ruby/prawn-table-0.2*
+ >=dev-ruby/rouge-1.8:*
+ >=dev-ruby/itextomml-1.5
+ >=dev-ruby/coderay-1.0.0
+ >=dev-ruby/ritex-1.0
+ >=dev-ruby/stringex-1.5.1"
+
+ruby_add_bdepend "doc? ( dev-ruby/rdoc )
+ test? ( >=dev-ruby/minitest-5.0 )"
+
+all_ruby_prepare() {
+ if ! use latex; then
+ # Remove latex tests. They will fail gracefully when latex isn't
+ # present at all, but not when components are missing (most
+ # notable ucs.sty).
+ sed -i -e '/latex -v/,/^ end/ s:^:#:' test/test_files.rb || die
+ fi
+
+ # Avoid tests requiring node to be installed with mathjaxnode or
+ # unpackaged katex.
+ rm -f test/testcases/span/math/{katex,mathjaxnode}* \
+ test/testcases/block/15_math/{katex,mathjaxnode}* || die
+}
+
+all_ruby_install() {
+ all_fakegem_install
+
+ doman man/man1/kramdown.1
+}
next reply other threads:[~2018-12-10 7:33 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 7:33 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-22 7:47 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/kramdown/ Hans de Graaff
2024-02-12 7:42 Hans de Graaff
2023-04-02 1:51 Sam James
2023-03-29 13:04 Sam James
2023-03-28 16:27 Sam James
2023-03-28 16:25 Sam James
2023-03-28 15:05 Sam James
2023-03-28 15:03 Sam James
2023-03-28 14:59 Sam James
2023-03-28 14:59 Sam James
2023-03-28 14:59 Sam James
2023-03-28 9:41 Hans de Graaff
2023-03-18 0:02 Sam James
2023-03-06 6:51 Hans de Graaff
2022-09-10 5:47 Hans de Graaff
2022-07-04 5:21 Hans de Graaff
2022-07-03 10:48 Agostino Sarubbo
2022-05-02 6:02 Hans de Graaff
2022-04-26 14:38 Sam James
2022-04-04 5:41 Hans de Graaff
2022-02-28 7:06 Yixun Lan
2022-02-10 10:20 Sam James
2021-12-24 23:55 Sam James
2021-12-18 2:10 Sam James
2021-11-10 12:49 Jakov Smolić
2021-08-29 18:30 Sam James
2021-08-27 10:29 Marek Szuba
2021-03-20 7:39 Hans de Graaff
2021-03-20 7:39 Hans de Graaff
2021-03-08 7:18 Hans de Graaff
2020-07-20 8:30 Hans de Graaff
2020-06-29 17:26 Hans de Graaff
2020-05-03 8:33 Hans de Graaff
2020-04-26 5:28 Hans de Graaff
2020-03-14 15:21 Hans de Graaff
2020-03-09 7:06 Hans de Graaff
2019-05-08 19:59 Hans de Graaff
2019-04-13 6:34 Hans de Graaff
2018-12-12 15:00 Hans de Graaff
2018-12-10 7:47 Hans de Graaff
2018-05-21 5:16 Hans de Graaff
2018-04-30 20:11 Hans de Graaff
2018-04-16 5:16 Hans de Graaff
2018-03-27 21:38 Aaron Bauman
2017-12-09 7:55 Hans de Graaff
2017-08-26 8:27 Hans de Graaff
2017-06-29 5:19 Hans de Graaff
2017-04-20 5:30 Hans de Graaff
2017-02-27 14:19 Michael Weber
2017-01-22 2:21 Manuel Rüger
2017-01-11 6:48 Hans de Graaff
2016-12-29 13:06 Hans de Graaff
2016-12-09 12:44 Hans de Graaff
2016-11-29 7:41 Hans de Graaff
2016-08-19 6:00 Hans de Graaff
2016-05-28 8:41 Hans de Graaff
2016-05-01 22:44 Manuel Rüger
2016-03-21 22:11 Manuel Rüger
2016-03-06 19:12 Manuel Rüger
2016-03-02 21:33 Manuel Rüger
2016-02-18 6:47 Hans de Graaff
2015-10-27 5:47 Hans de Graaff
2015-10-10 6:33 Jeroen Roovers
2015-08-30 6:29 Hans de Graaff
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=1544426624.7375b3c73ebc43278dd1ef5f90fbec15ee60cc9c.graaff@gentoo \
--to=graaff@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