From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/xmlrpc/
Date: Sun, 8 Jan 2017 07:25:26 +0000 (UTC) [thread overview]
Message-ID: <1483860316.8a9b39731068f3bd50908b6890182822ba87aaba.graaff@gentoo> (raw)
commit: 8a9b39731068f3bd50908b6890182822ba87aaba
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Sun Jan 8 07:25:16 2017 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sun Jan 8 07:25:16 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8a9b3973
dev-ruby/xmlrpc: avoid dependency on git, bug 604216
Avoid the need for a built-time dependency on dev-vcs/git.
Package-Manager: portage-2.3.0
dev-ruby/xmlrpc/xmlrpc-0.2.1.ebuild | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/dev-ruby/xmlrpc/xmlrpc-0.2.1.ebuild b/dev-ruby/xmlrpc/xmlrpc-0.2.1.ebuild
index c66b687..3edf785 100644
--- a/dev-ruby/xmlrpc/xmlrpc-0.2.1.ebuild
+++ b/dev-ruby/xmlrpc/xmlrpc-0.2.1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2016 Gentoo Foundation
+# Copyright 1999-2017 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Id$
@@ -24,4 +24,7 @@ IUSE=""
all_ruby_prepare() {
sed -i -e '/bundler/ s:^:#:' Rakefile || die
+
+ # Avoid dependency on git
+ sed -i -e 's/git ls-files -z/find * -print0/' ${RUBY_FAKEGEM_GEMSPEC} || die
}
next reply other threads:[~2017-01-08 7:25 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 7:25 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-17 4:38 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/xmlrpc/ Viorel Munteanu
2024-05-26 6:32 Hans de Graaff
2024-01-17 2:46 Ionen Wolkens
2023-12-29 14:54 Arthur Zamarin
2023-12-27 12:27 Arthur Zamarin
2023-12-27 12:27 Arthur Zamarin
2023-12-27 12:27 Arthur Zamarin
2023-12-27 12:27 Arthur Zamarin
2023-12-27 12:27 Arthur Zamarin
2023-12-27 12:27 Arthur Zamarin
2023-12-27 7:55 Hans de Graaff
2023-08-03 13:46 Hans de Graaff
2023-03-07 6:34 Hans de Graaff
2022-07-30 8:22 Hans de Graaff
2022-04-16 7:08 Hans de Graaff
2022-01-25 6:16 Hans de Graaff
2022-01-25 2:33 Sam James
2022-01-24 23:43 Sam James
2021-12-01 13:30 Agostino Sarubbo
2021-11-24 9:08 Agostino Sarubbo
2021-11-23 7:40 Agostino Sarubbo
2021-11-23 7:40 Agostino Sarubbo
2021-11-22 19:20 Sam James
2021-11-22 19:20 Sam James
2021-11-22 19:11 Hans de Graaff
2021-08-07 10:12 Hans de Graaff
2021-07-21 10:27 Marek Szuba
2021-02-07 5:58 Hans de Graaff
2021-01-06 18:32 Fabian Groffen
2020-11-23 6:41 Hans de Graaff
2019-12-26 11:06 Hans de Graaff
2019-06-24 15:14 Michael Haubenwallner
2019-04-27 19:48 Aaron Bauman
2018-12-30 3:43 Matt Turner
2018-12-27 2:57 Matt Turner
2018-12-26 8:20 Hans de Graaff
2018-12-25 11:11 Sergei Trofimovich
2018-12-15 14:25 Mikle Kolyada
2018-12-11 16:42 Thomas Deutschmann
2018-11-18 8:11 Hans de Graaff
2018-11-17 21:34 Thomas Deutschmann
2018-11-16 6:30 Hans de Graaff
2018-09-03 5:53 Hans de Graaff
2017-12-25 17:02 Hans de Graaff
2017-06-22 11:35 Fabian Groffen
2017-06-21 12:45 Fabian Groffen
2017-05-09 16:31 Richard Farina
2017-03-08 23:39 Michael Weber
2017-02-17 7:16 Hans de Graaff
2016-12-26 19:17 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=1483860316.8a9b39731068f3bd50908b6890182822ba87aaba.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