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] dev/graaff:master commit in: dev-ruby/acts-as-taggable-on/
Date: Fri, 17 Apr 2015 11:55:04 +0000 (UTC)	[thread overview]
Message-ID: <1429271653.808d44b5a1e30680ce388a4c5c79dc02d292a5a6.graaff@gentoo> (raw)

commit:     808d44b5a1e30680ce388a4c5c79dc02d292a5a6
Author:     Hans de Graaff <hans <AT> degraaff <DOT> org>
AuthorDate: Fri Apr 17 11:54:13 2015 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Fri Apr 17 11:54:13 2015 +0000
URL:        https://gitweb.gentoo.org/dev/graaff.git/commit/?id=808d44b5

Version bump.

Package-Manager: portage-2.2.14

 dev-ruby/acts-as-taggable-on/ChangeLog             |  6 ++++
 dev-ruby/acts-as-taggable-on/Manifest              |  1 +
 .../acts-as-taggable-on-3.5.0.ebuild               | 39 ++++++++++++++++++++++
 3 files changed, 46 insertions(+)

diff --git a/dev-ruby/acts-as-taggable-on/ChangeLog b/dev-ruby/acts-as-taggable-on/ChangeLog
index e9708a4..6465ddc 100644
--- a/dev-ruby/acts-as-taggable-on/ChangeLog
+++ b/dev-ruby/acts-as-taggable-on/ChangeLog
@@ -2,6 +2,12 @@
 # Copyright 1999-2015 Gentoo Foundation; Distributed under the GPL v2
 # $Header: $
 
+*acts-as-taggable-on-3.5.0 (17 Apr 2015)
+
+  17 Apr 2015; Hans de Graaff <graaff@gentoo.org>
+  +acts-as-taggable-on-3.5.0.ebuild:
+  Version bump.
+
   17 Apr 2015; Hans de Graaff <graaff@gentoo.org>
   -acts-as-taggable-on-3.1.0.ebuild, -acts-as-taggable-on-3.1.1.ebuild:
   Cleanup.

diff --git a/dev-ruby/acts-as-taggable-on/Manifest b/dev-ruby/acts-as-taggable-on/Manifest
index e3e52d8..4be579c 100644
--- a/dev-ruby/acts-as-taggable-on/Manifest
+++ b/dev-ruby/acts-as-taggable-on/Manifest
@@ -1,2 +1,3 @@
 DIST acts-as-taggable-on-3.1.1.gem 39936 SHA256 413795c45d2eb1f7c18f65b2d19768bfe8c306795de48e0eeea2decfb8e347cb SHA512 bbbd5331d97c5db77373dba9b4e3285207d3f7c49d2f9d7258f67b1303aadcf66cf461f33c09e96ff325a671d8da929d4c9f82410a8acb2a1f7842fef95953a2 WHIRLPOOL 3c10f9981dcc027319529c7a18a7e36fbb23898410e6c3499194f5881fb87826f7170b385d41fdda7be927c0579a93297b0f148f3648631613efe00ee7483b20
 DIST acts-as-taggable-on-3.2.6.gem 44544 SHA256 171a1e68a632cc9c9bc853f65c980db161ccb942c22dcc1a968d2333014fa12c SHA512 18ab71abb1dc8171222ff66a024b07be54ed9bad214dae3067294599b185bf4f9004e63852494ca7bab8f4953351099f6f126f15ec6466d5cd08fcaef4536bcb WHIRLPOOL 249e3b831303f71f5c170042e38962e3cc7a4380837198ef71dd0709f3e56d95f6acbb722385bb8a1d64cc733c24ca2d9f132bbfc66f65b3e65ddbe666af475f
+DIST acts-as-taggable-on-3.5.0.gem 49152 SHA256 27dfb17d01ed056c5d28b54142d356bac55953ce66259fa0fad28d4b1bfae02f SHA512 67086dd2b359d6f6d11a4c5ad319a6137030231a2515ef023b70e758d4274cfece06facd87e1f4cf31c777404a601c493dde0fe402af2a463dc27bb2f129fc8a WHIRLPOOL 27f6c76a8184eaa4e3199aeb3b06c61014e76c84a60e6fb179b27f0ec9cb1a985365a6ac2462b217a2fc814312543bbd5fd72122b6078570ee220aab697eaa38

diff --git a/dev-ruby/acts-as-taggable-on/acts-as-taggable-on-3.5.0.ebuild b/dev-ruby/acts-as-taggable-on/acts-as-taggable-on-3.5.0.ebuild
new file mode 100644
index 0000000..01d345c
--- /dev/null
+++ b/dev-ruby/acts-as-taggable-on/acts-as-taggable-on-3.5.0.ebuild
@@ -0,0 +1,39 @@
+# Copyright 1999-2015 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Header: $
+
+EAPI=5
+USE_RUBY="ruby19 ruby20 ruby21"
+
+RUBY_FAKEGEM_RECIPE_TEST="rspec"
+
+RUBY_FAKEGEM_TASK_DOC=""
+RUBY_FAKEGEM_EXTRADOC="CHANGELOG.md README.md UPGRADING.md"
+
+RUBY_FAKEGEM_EXTRAINSTALL="db"
+
+inherit ruby-fakegem versionator
+
+DESCRIPTION="Advanced tagging for Rails."
+HOMEPAGE="https://github.com/mbleigh/acts-as-taggable-on/"
+
+LICENSE="MIT"
+SLOT="$(get_version_component_range 1-2)"
+KEYWORDS="~amd64"
+IUSE=""
+
+# Compatibility issues with rspec-rails and test-unit autorunner. Now
+# also requires rspec 3.
+RESTRICT="test"
+
+ruby_add_rdepend ">=dev-ruby/rails-3.2 <dev-ruby/rails-5"
+
+#ruby_add_bdepend "test? ( dev-ruby/rspec:2 =dev-ruby/rspec-rails-2.13* >=dev-ruby/ammeter-0.1.3 dev-ruby/activerecord[sqlite3] )"
+
+all_ruby_prepare() {
+	sed -i -e '/git ls-files/d' ${PN}.gemspec || die
+
+	# Provide a database.yml file for sqlite3.
+	cp spec/internal/config/database.yml.sample spec/internal/config/database.yml || die
+	sed -i -e '/^mysql/,$d' spec/internal/config/database.yml || die
+}


             reply	other threads:[~2015-04-17 11:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 11:55 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-08-22 19:00 [gentoo-commits] dev/graaff:master commit in: dev-ruby/acts-as-taggable-on/ Hans de Graaff
2016-08-22 19:00 Hans de Graaff
2016-08-22 19:00 Hans de Graaff
2015-04-17 11:55 Hans de Graaff
2015-04-17 11:55 Hans de Graaff
2014-06-27  7:59 Hans de Graaff
2014-06-06  6:39 Hans de Graaff
2014-05-27  5:07 Hans de Graaff
2014-04-24 14:43 Hans de Graaff
2014-04-22 16:54 Hans de Graaff
2014-04-06  6:03 Hans de Graaff
2014-04-02 13:42 Hans de Graaff
2014-02-21 12:23 Hans de Graaff
2014-02-21 12:23 Hans de Graaff
2013-06-16  6:18 Hans de Graaff
2013-05-19  6:51 Hans de Graaff
2012-10-03  9:22 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=1429271653.808d44b5a1e30680ce388a4c5c79dc02d292a5a6.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