From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: www-apps/nanoc-core/
Date: Wed, 4 Oct 2023 05:31:14 +0000 (UTC) [thread overview]
Message-ID: <1696397471.318d7f79b88e04553b5a00b31aa29bcc37379162.graaff@gentoo> (raw)
commit: 318d7f79b88e04553b5a00b31aa29bcc37379162
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Wed Oct 4 05:30:22 2023 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Wed Oct 4 05:31:11 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=318d7f79
www-apps/nanoc-core: add 4.12.17
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
www-apps/nanoc-core/Manifest | 1 +
www-apps/nanoc-core/nanoc-core-4.12.17.ebuild | 77 +++++++++++++++++++++++++++
2 files changed, 78 insertions(+)
diff --git a/www-apps/nanoc-core/Manifest b/www-apps/nanoc-core/Manifest
index b9aaed5f1857..090b7c8c8714 100644
--- a/www-apps/nanoc-core/Manifest
+++ b/www-apps/nanoc-core/Manifest
@@ -1 +1,2 @@
DIST nanoc-core-4.12.16.tar.gz 350823 BLAKE2B 8196589290b5120b74bd2063e60f1fad14af98f7c8ffcef0a226d28ecb3f129ab04c913ad921e64c9551965c8fe1e26da1e0f41baa64a75caa372d6796c5084b SHA512 e04a562d87250286a9fbdc0381fdc64868f87f67d1ae9ce81f0e21c13496e168cfc4936c02b3cba87e8d647ab070670a208722fd53f4265eb3674b7ba20ccebd
+DIST nanoc-core-4.12.17.tar.gz 350964 BLAKE2B ca19c259eac8005f2612f61b902005d43196e3e01e8bb0c7a77f9f68bc27486ad6e6e9860420817a633b9a48973f7d98689046cbdb6fe4c185ae18583168d6d2 SHA512 d5a8d3711642f65078102be9317ac2b7db3635c5ff5616d2c05fd917e5cba76a8a21ceeb0a84565723d334f8d62cb55c8097eac07c9bc30f783916c8d312b8c1
diff --git a/www-apps/nanoc-core/nanoc-core-4.12.17.ebuild b/www-apps/nanoc-core/nanoc-core-4.12.17.ebuild
new file mode 100644
index 000000000000..80ccfe943d17
--- /dev/null
+++ b/www-apps/nanoc-core/nanoc-core-4.12.17.ebuild
@@ -0,0 +1,77 @@
+# Copyright 1999-2023 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+USE_RUBY="ruby31 ruby32"
+
+RUBY_FAKEGEM_EXTRADOC="NEWS.md README.md"
+
+RUBY_FAKEGEM_GEMSPEC="${PN}.gemspec"
+
+inherit ruby-fakegem
+
+DESCRIPTION="nanoc is a simple but very flexible static site generator written in Ruby"
+HOMEPAGE="https://nanoc.app/"
+SRC_URI="https://github.com/nanoc/nanoc/archive/${PV}.tar.gz -> ${P}.tar.gz"
+LICENSE="MIT"
+
+KEYWORDS="~amd64 ~riscv"
+SLOT="0"
+IUSE="${IUSE} minimal"
+
+DEPEND+="test? ( app-text/asciidoc app-text/highlight )"
+
+RUBY_S="nanoc-${PV}/nanoc-core"
+
+ruby_add_rdepend "
+ >=dev-ruby/concurrent-ruby-1.1:1
+ dev-ruby/ddmetrics:1
+ dev-ruby/ddplugin:1
+ >=dev-ruby/immutable-ruby-0.1:0
+ >=dev-ruby/json_schema-0.19:0
+ >=dev-ruby/memo_wise-1.5:1
+ dev-ruby/psych:0
+ dev-ruby/slow_enumerator_tools:1
+ >=dev-ruby/tty-platform-0.2:0
+ >=dev-ruby/zeitwerk-2.1:2
+"
+
+ruby_add_bdepend "test? (
+ dev-ruby/bundler
+ dev-ruby/rspec:3
+ dev-ruby/rspec-its
+ dev-ruby/fuubar
+ dev-ruby/minitest
+ dev-ruby/timecop
+ dev-ruby/tty-command
+ dev-ruby/yard
+ www-apps/nanoc-spec
+)
+"
+
+PATCHES=( "${FILESDIR}/${PN}-4.12.2-contracts.patch" )
+
+all_ruby_prepare() {
+ # Avoid unneeded development dependencies
+ sed -i -e '/simplecov/I s:^:#:' \
+ -e '/codecov/I s:^:#:' ../common/spec/spec_helper_head_core.rb || die
+ sed -e '/coverall/I s:^:#:' \
+ -e '/rubocop/ s:^:#:' \
+ -i Rakefile || die
+ sed -i -e '2i require "tmpdir"; require "pathname"; gem "psych", "~> 4.0"' spec/spec_helper.rb || die
+
+ echo "-r ./spec/spec_helper.rb" > .rspec || die
+
+ sed -i -e "s:require_relative 'lib:require './lib:" ${RUBY_FAKEGEM_GEMSPEC} || die
+
+ # Use useable tmp dir
+ sed -i -e "s:/tmp/whatever:${T}/whatever:" spec/nanoc/core/checksummer_spec.rb || die
+
+ # Avoid circular dependency on www-apps/nanoc
+ sed -i -e '/.all_outdated/,/^ end/ s:^:#:' spec/nanoc/core/feature_spec.rb || die
+ rm -f spec/nanoc/core_spec.rb || die
+}
+
+each_ruby_test() {
+ RUBYLIB="${S}/lib" ${RUBY} -S rake spec || die
+}
next reply other threads:[~2023-10-04 5:31 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 5:31 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-29 12:21 [gentoo-commits] repo/gentoo:master commit in: www-apps/nanoc-core/ Hans de Graaff
2024-11-09 7:40 Hans de Graaff
2024-11-09 7:40 Hans de Graaff
2024-06-22 6:18 Hans de Graaff
2024-06-22 6:18 Hans de Graaff
2024-04-28 8:35 Hans de Graaff
2024-03-17 8:17 Hans de Graaff
2023-12-29 10:14 Hans de Graaff
2023-08-11 19:14 Hans de Graaff
2023-07-18 7:23 Hans de Graaff
2023-06-25 5:51 Hans de Graaff
2023-06-15 6:24 Hans de Graaff
2023-03-29 6:35 Hans de Graaff
2022-12-18 7:21 Hans de Graaff
2022-11-09 19:50 Arthur Zamarin
2022-10-09 7:22 Hans de Graaff
2022-10-09 7:22 Hans de Graaff
2022-08-23 5:34 Sam James
2022-07-10 6:33 Hans de Graaff
2022-06-18 8:40 Hans de Graaff
2022-05-29 5:50 Hans de Graaff
2022-04-10 5:06 Hans de Graaff
2022-03-18 6:50 Jakov Smolić
2021-11-14 8:10 Hans de Graaff
2021-07-12 6:52 Hans de Graaff
2021-07-06 8:37 Hans de Graaff
2019-09-29 9:07 Hans de Graaff
2019-09-29 9:07 Hans de Graaff
2019-09-11 7:43 Hans de Graaff
2019-09-07 6:10 Hans de Graaff
2019-08-18 5:44 Hans de Graaff
2019-08-18 5:44 Hans de Graaff
2019-08-10 3:28 Hans de Graaff
2019-07-30 6:08 Hans de Graaff
2019-07-07 6:30 Hans de Graaff
2019-06-16 8:25 Hans de Graaff
2019-05-10 5:40 Hans de Graaff
2019-04-08 5:19 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=1696397471.318d7f79b88e04553b5a00b31aa29bcc37379162.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