public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
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: Sun, 26 Apr 2020 05:28:03 +0000 (UTC)	[thread overview]
Message-ID: <1587878713.6e8fc321e04d978dd4c8a3b535fbcffe955ee521.graaff@gentoo> (raw)

commit:     6e8fc321e04d978dd4c8a3b535fbcffe955ee521
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 26 05:23:14 2020 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sun Apr 26 05:25:13 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6e8fc321

dev-ruby/kramdown: add 2.2.1

Package-Manager: Portage-2.3.89, Repoman-2.3.20
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>

 dev-ruby/kramdown/Manifest              |  1 +
 dev-ruby/kramdown/kramdown-2.2.1.ebuild | 52 +++++++++++++++++++++++++++++++++
 2 files changed, 53 insertions(+)

diff --git a/dev-ruby/kramdown/Manifest b/dev-ruby/kramdown/Manifest
index 3a6f83a6ab9..8839ea91c17 100644
--- a/dev-ruby/kramdown/Manifest
+++ b/dev-ruby/kramdown/Manifest
@@ -1,2 +1,3 @@
 DIST kramdown-1.17.0.gem 260608 BLAKE2B 56f0abb2c94ab2de31bcd71940c22610efc8143c434295627513735b5983a369b0d9b36a88477a4e0b14bb23a3d314280702655c854cb7134e29bebc1f276966 SHA512 0f98f4234dec41b53d7f116be1075176c7fcbf21621c6f52a9e5b4055a777b01f1a0a912be81a651e85df022e7bab3ac183ee66cd87abeae092cd1920aceff04
 DIST kramdown-2.1.0.gem 119808 BLAKE2B a5beac52349fb49d315d83391d52574013bd76e084edb25a0b3bc0d813fc5b0dae0799a03bdd20fb500560effc94ad8f262fab9bbb8eef275aaead3405d3a64c SHA512 86a2934218365c71ff4f99591cba3b49ddc5ee60a78fcd7bf1f72e86281cda7bbea3c67b1b7caca6c4b8ca6e5b62d4df25e85089db659c93bd4da4b1c8eada69
+DIST kramdown-2.2.1.gem 121344 BLAKE2B e1da7e1289b64cc3d4db253330405b03b1a430a690e2f5b32970dc8c1d52bbf1f418e8aa1c597a3333141c3974893e1532e870a131fc297b9080b66bc6918882 SHA512 7c322010a8a418706c48d5a1011354aba215d50be94354fff93a636ff3453906bb381cf5669560a6bd10ecaf3bab7b04f446efa0a4b85322865b879f74de4c43

diff --git a/dev-ruby/kramdown/kramdown-2.2.1.ebuild b/dev-ruby/kramdown/kramdown-2.2.1.ebuild
new file mode 100644
index 00000000000..043e2577000
--- /dev/null
+++ b/dev-ruby/kramdown/kramdown-2.2.1.ebuild
@@ -0,0 +1,52 @@
+# Copyright 1999-2020 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+USE_RUBY="ruby24 ruby25 ruby26"
+
+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="$(ver_cut 1)"
+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/rexml
+	>=dev-ruby/rouge-1.8
+	>=dev-ruby/stringex-1.5.1
+	!!<dev-ruby/kramdown-1.17.0-r2:0"
+
+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
+}
+
+each_ruby_test() {
+	${RUBY} -Ilib:. -e "Dir['test/test_*.rb'].each{|f| require f}" || die
+}
+
+all_ruby_install() {
+	all_fakegem_install
+
+	doman man/man1/kramdown.1
+}


             reply	other threads:[~2020-04-26  5:28 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-26  5:28 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-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-12-10  7:33 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=1587878713.6e8fc321e04d978dd4c8a3b535fbcffe955ee521.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