From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/barby/
Date: Sun, 2 Feb 2020 16:20:35 +0000 (UTC) [thread overview]
Message-ID: <1580660426.70c51977816777c5db1a7b83aa43d36e129bb828.graaff@gentoo> (raw)
commit: 70c51977816777c5db1a7b83aa43d36e129bb828
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 2 16:20:03 2020 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sun Feb 2 16:20:26 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=70c51977
dev-ruby/barby: cleanup
Package-Manager: Portage-2.3.84, Repoman-2.3.20
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-ruby/barby/Manifest | 1 -
dev-ruby/barby/barby-0.6.7.ebuild | 99 ---------------------------------------
2 files changed, 100 deletions(-)
diff --git a/dev-ruby/barby/Manifest b/dev-ruby/barby/Manifest
index a8986389d87..cffe78877a3 100644
--- a/dev-ruby/barby/Manifest
+++ b/dev-ruby/barby/Manifest
@@ -1,2 +1 @@
-DIST barby-0.6.7.tar.gz 95199 BLAKE2B b1729e361a41deee248a3c74c56d072fe0eeb3463ff4730744736e1a523f2844e877d63b058ec02e4cdad1f77620bcd476e823864428aff78b462cf29b20909a SHA512 29ba52612b2390ebd2a9e0acc0eec4a4c119ca305662f47e6656cb63727956877970d14f9b924466fad6e9e927e23f74c2614b41e09ca6b068bdabbaae21f93f
DIST barby-0.6.8.tar.gz 96647 BLAKE2B b0af8e5573dc7d3d1881c793895d1c440b97bb5609b0759f56bdecfed7b4b74080f96301d2511101abb21760074584905fdc4e94938d38e2a553933686ccf976 SHA512 1d51dece22febd8c8a234241b88edd3ea93eae328e69fbd8dba3f48afcea7943ec4a72252a74b476aae5812ee132de6b87e37f9fd4c2a43d7c79ec68c831b68c
diff --git a/dev-ruby/barby/barby-0.6.7.ebuild b/dev-ruby/barby/barby-0.6.7.ebuild
deleted file mode 100644
index c6bb8935472..00000000000
--- a/dev-ruby/barby/barby-0.6.7.ebuild
+++ /dev/null
@@ -1,99 +0,0 @@
-# Copyright 1999-2019 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=6
-
-USE_RUBY="ruby24 ruby25"
-
-RUBY_FAKEGEM_TASK_TEST="test"
-
-RUBY_FAKEGEM_EXTRADOC="CHANGELOG README.md"
-
-RUBY_FAKEGEM_GEMSPEC="${PN}.gemspec"
-
-inherit ruby-fakegem
-
-DESCRIPTION="Ruby barcode generator that doesn't rely on 3rd party libraries"
-HOMEPAGE="http://toreto.re/barby/"
-
-GITHUB_USER="toretore"
-SRC_URI="https://github.com/${GITHUB_USER}/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
-
-LICENSE="MIT"
-SLOT="0"
-KEYWORDS="~amd64"
-IUSE="test qrcode rmagick prawn png cairo"
-
-ruby_add_rdepend "
- rmagick? ( dev-ruby/rmagick )
- cairo? ( dev-ruby/rcairo )"
-
-ruby_add_rdepend "qrcode? ( dev-ruby/rqrcode )
- png? ( dev-ruby/chunky_png )
- prawn? ( dev-ruby/prawn:* )"
-
-ruby_add_bdepend "test? ( dev-ruby/minitest )"
-
-# testing requires imagemagick capable of png output
-DEPEND+=" test? ( media-gfx/imagemagick[png] )"
-
-# prawn breaks tests for some reasons, needs to be investigated; code
-# still works though.
-RESTRICT+=" prawn? ( test )"
-
-all_ruby_prepare() {
- sed -i -e 's/README/README.md/' Rakefile || die
-
- sed -i -e '/[bB]undler/s:^:#:' test/test_helper.rb || die
-
- if use qrcode; then
- sed -i -e '/^end/i s.add_dependency "rqrcode"' ${RUBY_FAKEGEM_GEMSPEC}
- else
- rm \
- lib/barby/barcode/qr_code.rb \
- test/qr_code_test.rb
- fi
-
- if use rmagick; then
- sed -i -e '/^end/i s.add_dependency "rmagick"' ${RUBY_FAKEGEM_GEMSPEC}
- else
- rm \
- lib/barby/outputter/rmagick_outputter.rb \
- test/outputter/rmagick_outputter_test.rb
- fi
-
- if use prawn; then
- sed -i -e '/^end/i s.add_dependency "prawn"' ${RUBY_FAKEGEM_GEMSPEC}
- else
- rm \
- lib/barby/outputter/prawn_outputter.rb \
- test/outputter/prawn_outputter_test.rb
- fi
-
- if use png; then
- sed -i -e '/^end/i s.add_dependency "chunky_png"' ${RUBY_FAKEGEM_GEMSPEC}
- else
- rm \
- lib/barby/outputter/png_outputter.rb \
- test/outputter/png_outputter_test.rb
- fi
-
- if use cairo; then
- sed -i -e '/^end/i s.add_dependency "cairo"' ${RUBY_FAKEGEM_GEMSPEC}
- else
- rm \
- lib/barby/outputter/cairo_outputter.rb \
- test/outputter/cairo_outputter_test.rb
- fi
-
- rm -f \
- lib/barby/barcode/data_matrix.rb \
- test/data_matrix_test.rb \
- lib/barby/outputter/pdfwriter_outputter.rb \
- test/outputter/pdfwriter_outputter_test.rb || die
-
- sed -i \
- -e '/semacode/d' \
- -e '/pdf-writer/d' \
- ${RUBY_FAKEGEM_GEMSPEC} || die
-}
next reply other threads:[~2020-02-02 16:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 16:20 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-18 9:28 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/barby/ Hans de Graaff
2023-09-18 5:21 Hans de Graaff
2023-09-15 14:56 Hans de Graaff
2023-03-25 7:12 Sam James
2020-08-04 3:40 Hans de Graaff
2020-02-09 10:59 Hans de Graaff
2019-12-12 16:46 Michał Górny
2019-11-17 6:06 Hans de Graaff
2019-07-10 4:58 Hans de Graaff
2019-05-25 5:38 Hans de Graaff
2019-05-23 5:39 Hans de Graaff
2019-04-11 18:29 Hans de Graaff
2018-12-13 8:09 Hans de Graaff
2018-08-14 4:02 Hans de Graaff
2018-04-19 19:37 Hans de Graaff
2017-08-27 6:18 Hans de Graaff
2017-08-27 6:18 Hans de Graaff
2016-12-02 7:29 Hans de Graaff
2016-05-15 5:35 Hans de Graaff
2016-04-22 5:07 Hans de Graaff
2016-04-21 5:17 Hans de Graaff
2016-03-27 21:52 Manuel Rüger
2016-03-27 21:52 Manuel Rüger
2015-08-11 17:30 Peter Wilmott
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=1580660426.70c51977816777c5db1a7b83aa43d36e129bb828.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