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/mini_magick/
Date: Sat,  6 Aug 2016 09:26:24 +0000 (UTC)	[thread overview]
Message-ID: <1470475576.aa23a6d8c31d9b992803f99a6367550428d33e86.graaff@gentoo> (raw)

commit:     aa23a6d8c31d9b992803f99a6367550428d33e86
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sat Aug  6 09:25:29 2016 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sat Aug  6 09:26:16 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=aa23a6d8

dev-ruby/mini_magick: add 4.5.1

Package-Manager: portage-2.2.28

 dev-ruby/mini_magick/Manifest                 |  1 +
 dev-ruby/mini_magick/mini_magick-4.5.1.ebuild | 48 +++++++++++++++++++++++++++
 2 files changed, 49 insertions(+)

diff --git a/dev-ruby/mini_magick/Manifest b/dev-ruby/mini_magick/Manifest
index 6fa47ba..9315340 100644
--- a/dev-ruby/mini_magick/Manifest
+++ b/dev-ruby/mini_magick/Manifest
@@ -1 +1,2 @@
 DIST mini_magick-4.4.0.tar.gz 1111535 SHA256 ee1d74693d569c15bc421b39ca35f66b4afe5aa08cdf81d4bbff096fe308833a SHA512 5b6bc158f04175676fac100f17c82694ab6d20845f44ba6965b20533e139581694a641a96d7cb8ad323949f6b490ea20b96a1b9b576d7b9482269c8592df57d5 WHIRLPOOL 3ba4e177c63f265365c60a5ffeef3d9a0511ab061cd819df34fdc127fc8886e125bf85e64b869a21a7d28c1fe4e61cba0a1da96e1c1e09314e3ea473c844898d
+DIST mini_magick-4.5.1.tar.gz 1113157 SHA256 4222e9c8b84914230669e0a180a2e1d68e6c3d0d2b9e2464faf664bd545e8522 SHA512 d586f8a33e1050923311bbd26209ba01488b5249335a19898df47479e4dfca25fba33db6dd57da420e73fbc48eab27723fb4937a7a932c1b39143bfd02bea654 WHIRLPOOL 623b01092ff2e4647a318ee67025d04cdacba252dcae87139d88a1eef535262af38a80d72f08b49cf6889d0ec95a876bfd2482ef66e5b4242f92ea3075fb0705

diff --git a/dev-ruby/mini_magick/mini_magick-4.5.1.ebuild b/dev-ruby/mini_magick/mini_magick-4.5.1.ebuild
new file mode 100644
index 0000000..604cd25
--- /dev/null
+++ b/dev-ruby/mini_magick/mini_magick-4.5.1.ebuild
@@ -0,0 +1,48 @@
+# Copyright 1999-2016 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Id$
+
+EAPI=5
+
+USE_RUBY="ruby20 ruby21 ruby22"
+
+RUBY_FAKEGEM_RECIPE_TEST="rspec3"
+RUBY_FAKEGEM_RECIPE_DOC="rdoc"
+RUBY_FAKEGEM_EXTRADOC="README.md"
+
+RUBY_FAKEGEM_GEMSPEC="${PN}.gemspec"
+
+RUBY_FAKEGEM_BINWRAP=""
+
+inherit ruby-fakegem eutils
+
+DESCRIPTION="Manipulate images with minimal use of memory"
+HOMEPAGE="https://github.com/minimagick/minimagick"
+SRC_URI="https://github.com/minimagick/minimagick/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+RUBY_S="minimagick-${PV}"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~amd64"
+IUSE=""
+
+# It's only used at runtime in this case because this extension only
+# _calls_ the commands. But when we run tests we're going to need tiff
+# and jpeg support at a minimum.
+RDEPEND+=" media-gfx/imagemagick"
+DEPEND+=" test? ( media-gfx/imagemagick[tiff,jpeg,png] >=media-gfx/graphicsmagick-1.3.20[tiff,jpeg,png] )"
+
+ruby_add_bdepend "test? ( dev-ruby/mocha dev-ruby/posix-spawn )"
+
+all_ruby_prepare() {
+	# remove executable bit from all files
+	find "${S}" -type f -exec chmod -x {} +
+
+	sed -i -e '/\([Bb]undler\|pry\)/ s:^:#:' spec/spec_helper.rb || die
+
+	# Don't force a specific formatter but use overall Gentoo defaults.
+	sed -i -e '/config.formatter/d' spec/spec_helper.rb || die
+
+	# Avoid broken spec that does not assume . in path name
+	sed -i -e '/reformats a layer/,/end/ s:^:#:' spec/lib/mini_magick/image_spec.rb || die
+}


             reply	other threads:[~2016-08-06  9:26 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-06  9:26 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-20 15:53 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/mini_magick/ Hans de Graaff
2025-07-12  5:02 Hans de Graaff
2025-06-03 10:53 Hans de Graaff
2025-06-03 10:53 Hans de Graaff
2025-04-26  5:27 Hans de Graaff
2025-04-26  5:27 Hans de Graaff
2025-02-23  8:40 Hans de Graaff
2025-02-03  6:43 Hans de Graaff
2025-02-02  7:04 Hans de Graaff
2025-02-02  7:04 Hans de Graaff
2025-01-13  7:09 Hans de Graaff
2024-09-01  6:34 Hans de Graaff
2024-08-21  9:19 Joonas Niilola
2024-07-15  7:47 Hans de Graaff
2024-07-15  7:47 Hans de Graaff
2024-06-28  4:31 Hans de Graaff
2024-06-28  4:31 Hans de Graaff
2024-06-14  4:52 Hans de Graaff
2024-05-18 17:23 Hans de Graaff
2023-07-02 10:24 Hans de Graaff
2023-04-07 18:25 Sam James
2023-03-28 20:20 Sam James
2023-03-28 20:16 Sam James
2023-03-21  5:21 Hans de Graaff
2022-12-11  6:27 Hans de Graaff
2022-12-04 15:08 Hans de Graaff
2022-07-29  4:48 Hans de Graaff
2022-06-13  8:06 Yixun Lan
2022-04-09  7:38 Hans de Graaff
2021-07-07  8:31 Hans de Graaff
2021-02-18  7:30 Hans de Graaff
2020-11-08  6:33 Hans de Graaff
2020-09-11  6:58 Hans de Graaff
2020-05-23 17:41 Hans de Graaff
2020-01-07  6:08 Hans de Graaff
2020-01-07  6:08 Hans de Graaff
2019-08-30  6:39 Hans de Graaff
2019-07-16  6:56 Hans de Graaff
2019-05-04 19:14 Hans de Graaff
2019-04-13  6:34 Hans de Graaff
2019-02-25  6:55 Hans de Graaff
2019-01-03 19:23 Sergei Trofimovich
2019-01-03 19:23 Sergei Trofimovich
2018-09-22  5:47 Hans de Graaff
2018-08-06  8:16 Sergei Trofimovich
2018-06-12 11:36 Thomas Deutschmann
2018-05-19  7:51 Hans de Graaff
2018-04-29 17:09 Hans de Graaff
2018-02-04 15:15 Hans de Graaff
2017-07-19  6:55 Hans de Graaff
2017-05-30  4:30 Hans de Graaff
2016-10-31  1:29 Manuel Rüger
2016-03-22 21:56 Manuel Rüger
2016-02-07  7:22 Hans de Graaff
2016-02-07  7:22 Hans de Graaff
2015-10-21  5:19 Hans de Graaff
2015-10-04  6:54 Hans de Graaff
2015-10-04  6:54 Hans de Graaff
2015-09-12  5:19 Hans de Graaff
2015-08-19 18:27 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=1470475576.aa23a6d8c31d9b992803f99a6367550428d33e86.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