From: "Hans de Graaff (graaff)" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-ruby/ruby-progressbar: ChangeLog ruby-progressbar-0.9.ebuild
Date: Mon, 24 Aug 2009 20:00:51 +0000 [thread overview]
Message-ID: <E1Mffil-0007nk-IJ@stork.gentoo.org> (raw)
graaff 09/08/24 20:00:51
Modified: ChangeLog
Added: ruby-progressbar-0.9.ebuild
Log:
Version bump.
(Portage version: 2.1.6.13/cvs/Linux x86_64)
Revision Changes Path
1.18 dev-ruby/ruby-progressbar/ChangeLog
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/ruby-progressbar/ChangeLog?rev=1.18&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/ruby-progressbar/ChangeLog?rev=1.18&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/ruby-progressbar/ChangeLog?r1=1.17&r2=1.18
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-ruby/ruby-progressbar/ChangeLog,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- ChangeLog 15 May 2009 14:49:46 -0000 1.17
+++ ChangeLog 24 Aug 2009 20:00:51 -0000 1.18
@@ -1,6 +1,12 @@
# ChangeLog for dev-ruby/ruby-progressbar
# Copyright 1999-2009 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-ruby/ruby-progressbar/ChangeLog,v 1.17 2009/05/15 14:49:46 flameeyes Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-ruby/ruby-progressbar/ChangeLog,v 1.18 2009/08/24 20:00:51 graaff Exp $
+
+*ruby-progressbar-0.9 (24 Aug 2009)
+
+ 24 Aug 2009; Hans de Graaff <graaff@gentoo.org>
+ +ruby-progressbar-0.9.ebuild:
+ Version bump.
15 May 2009; Diego E. Pettenò <flameeyes@gentoo.org>
ruby-progressbar-0.8.ebuild:
1.1 dev-ruby/ruby-progressbar/ruby-progressbar-0.9.ebuild
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/ruby-progressbar/ruby-progressbar-0.9.ebuild?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/ruby-progressbar/ruby-progressbar-0.9.ebuild?rev=1.1&content-type=text/plain
Index: ruby-progressbar-0.9.ebuild
===================================================================
# Copyright 1999-2009 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/dev-ruby/ruby-progressbar/ruby-progressbar-0.9.ebuild,v 1.1 2009/08/24 20:00:51 graaff Exp $
inherit ruby
DESCRIPTION="A Text Progress Bar Library for Ruby"
HOMEPAGE="http://0xcc.net/ruby-progressbar/"
SRC_URI="http://0xcc.net/ruby-progressbar/${P}.tar.gz"
LICENSE="Ruby"
SLOT="0"
USE_RUBY="ruby18"
KEYWORDS="~alpha ~amd64 ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86 ~x86-fbsd"
IUSE=""
src_test() {
${RUBY} -I. test.rb || die "test failed"
}
src_install() {
rm test.rb
ruby_src_install
}
next reply other threads:[~2009-08-24 20:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 20:00 Hans de Graaff (graaff) [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-24 17:22 [gentoo-commits] gentoo-x86 commit in dev-ruby/ruby-progressbar: ChangeLog ruby-progressbar-0.9.ebuild Jeroen Roovers (jer)
2009-12-24 17:24 Jeroen Roovers (jer)
2010-01-10 20:56 Markus Meier (maekke)
2010-01-11 18:11 Raul Porcel (armin76)
2010-01-14 1:09 Brent Baude (ranger)
2010-08-01 16:35 Diego Petteno (flameeyes)
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=E1Mffil-0007nk-IJ@stork.gentoo.org \
--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