From: "Georgy Yakovlev" <gyakovlev@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-emulation/vagrant/
Date: Sun, 30 Dec 2018 20:53:54 +0000 (UTC) [thread overview]
Message-ID: <1546203216.36639d91c3ffede7e52fae2205b78507c458fd7d.gyakovlev@gentoo> (raw)
commit: 36639d91c3ffede7e52fae2205b78507c458fd7d
Author: Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
AuthorDate: Sun Dec 30 20:17:49 2018 +0000
Commit: Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
CommitDate: Sun Dec 30 20:53:36 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=36639d91
app-emulation/vagrant: revbump, loosen deps
Closes: https://bugs.gentoo.org/674008
Package-Manager: Portage-2.3.53, Repoman-2.3.12
Signed-off-by: Georgy Yakovlev <gyakovlev <AT> gentoo.org>
app-emulation/vagrant/vagrant-2.2.2-r2.ebuild | 90 +++++++++++++++++++++++++++
1 file changed, 90 insertions(+)
diff --git a/app-emulation/vagrant/vagrant-2.2.2-r2.ebuild b/app-emulation/vagrant/vagrant-2.2.2-r2.ebuild
new file mode 100644
index 00000000000..a2515b61584
--- /dev/null
+++ b/app-emulation/vagrant/vagrant-2.2.2-r2.ebuild
@@ -0,0 +1,90 @@
+# Copyright 1999-2018 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=6
+USE_RUBY="ruby23 ruby24 ruby25"
+
+RUBY_FAKEGEM_EXTRADOC="CHANGELOG.md README.md"
+RUBY_FAKEGEM_GEMSPEC="vagrant.gemspec"
+RUBY_FAKEGEM_EXTRAINSTALL="keys plugins templates version.txt"
+RUBY_FAKEGEM_TASK_DOC=""
+
+inherit bash-completion-r1 ruby-fakegem
+
+DESCRIPTION="A tool for building and distributing development environments"
+HOMEPAGE="https://vagrantup.com/"
+SRC_URI="https://github.com/hashicorp/vagrant/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~amd64"
+IUSE="+virtualbox"
+RESTRICT="test"
+
+RDEPEND="${RDEPEND}
+ app-arch/libarchive
+ net-misc/curl
+ virtualbox? ( || ( app-emulation/virtualbox app-emulation/virtualbox-bin ) )"
+
+ruby_add_rdepend "
+ >=dev-ruby/bcrypt_pbkdf-1.0.0
+ >=dev-ruby/childprocess-0.6.0
+ >=dev-ruby/ed25519-1.2.4
+ >=dev-ruby/erubis-2.7.0
+ >=dev-ruby/hashicorp-checkpoint-0.1.5
+ >=dev-ruby/i18n-1.1.1:1
+ >=dev-ruby/listen-3.1.5
+ <dev-ruby/log4r-1.1.11
+ <dev-ruby/mime-types-3:*
+ >=dev-ruby/net-ssh-5.0.0:*
+ >=dev-ruby/net-sftp-2.1
+ >=dev-ruby/net-scp-1.2.0
+ dev-ruby/rest-client:2
+ >=dev-ruby/rubyzip-1.2.2
+ >=dev-ruby/vagrant_cloud-2.0.0
+"
+
+# upstream specifies rake>=12 but it apparently doesn't need something this
+# recent. Because vagrant builds fine with rake 10 and because stabilizing rake
+# is tricky, we specify a lower dependency requirement here. This way, we'll be
+# able to stabilize vagrant sooner.
+ruby_add_bdepend "
+ >=dev-ruby/rake-10.5.0
+"
+
+all_ruby_prepare() {
+ # remove bundler support
+ sed -i '/[Bb]undler/d' Rakefile || die
+ rm Gemfile || die
+
+ # loosen dependencies
+ sed -e '/hashicorp-checkpoint\|i18n\|listen\|net-ssh\|net-scp\|rake\|childprocess/s/~>/>=/' \
+ -e '/ruby_dep/s/<=/>=/' \
+ -i ${PN}.gemspec || die
+
+ # remove windows-specific gems
+ sed -e '/wdm\|winrm/d' \
+ -i ${PN}.gemspec || die
+
+ # remove bsd-specific gems
+ sed -e '/rb-kqueue/d' \
+ -i ${PN}.gemspec || die
+
+ sed -e "s/@VAGRANT_VERSION@/${PV}/g" "${FILESDIR}/${PN}.in" > "${PN}" || die
+}
+
+all_ruby_install() {
+ all_fakegem_install
+
+ newbashcomp contrib/bash/completion.sh ${PN}
+
+ # provide executable similar to upstream:
+ # https://github.com/hashicorp/vagrant-installers/blob/master/substrate/modules/vagrant_installer/templates/vagrant.erb
+ dobin "${PN}"
+
+ # directory for plugins.json
+ keepdir /var/lib/vagrant
+
+ insinto /usr/share/vim/vimfiles/syntax/
+ doins contrib/vim/vagrantfile.vim
+}
next reply other threads:[~2018-12-30 20:54 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 20:53 Georgy Yakovlev [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-20 7:44 [gentoo-commits] repo/gentoo:master commit in: app-emulation/vagrant/ Joonas Niilola
2024-04-20 7:44 Joonas Niilola
2024-02-02 1:24 Sam James
2024-01-31 12:54 Joonas Niilola
2023-09-10 11:41 Hans de Graaff
2023-08-27 18:56 Arthur Zamarin
2023-03-18 1:22 Sam James
2023-03-18 1:22 Sam James
2022-12-28 20:37 Sam James
2022-08-17 15:39 Sam James
2022-05-20 8:40 Joonas Niilola
2022-05-20 8:40 Joonas Niilola
2021-10-20 3:02 Sam James
2021-09-28 19:47 Sam James
2021-09-28 19:47 Sam James
2021-09-28 1:01 Sam James
2020-07-11 6:03 Georgy Yakovlev
2020-05-21 6:59 Georgy Yakovlev
2020-05-19 3:26 Georgy Yakovlev
2020-03-13 5:43 Georgy Yakovlev
2020-01-28 19:59 Georgy Yakovlev
2019-10-25 20:39 Georgy Yakovlev
2019-06-26 19:07 Georgy Yakovlev
2019-05-20 18:56 Georgy Yakovlev
2019-02-27 19:29 Georgy Yakovlev
2019-01-10 3:32 Georgy Yakovlev
2018-12-30 20:53 Georgy Yakovlev
2018-12-13 0:42 Georgy Yakovlev
2018-12-13 0:42 Georgy Yakovlev
2018-12-12 10:20 Hans de Graaff
2018-11-30 5:29 Georgy Yakovlev
2018-11-30 5:29 Georgy Yakovlev
2018-09-26 20:02 Georgy Yakovlev
2018-07-24 18:54 Virgil Dupras
2018-06-27 16:58 Georgy Yakovlev
2018-05-11 10:13 Michał Górny
2018-05-11 10:13 Michał Górny
2018-05-11 10:13 Michał Górny
2018-04-20 9:00 Amy Liffey
2018-02-13 15:53 Michał Górny
2018-02-13 15:53 Michał Górny
2017-09-21 14:51 Amy Liffey
2017-09-10 21:24 Patrice Clement
2017-02-11 11:33 Michael Palimaka
2016-09-27 14:56 Amy Winston
2016-08-06 13:13 Sebastian Pipping
2016-08-06 13:05 Sebastian Pipping
2016-01-20 9:01 Patrice Clement
2016-01-20 9:01 Patrice Clement
2016-01-20 7:19 Ian Delaney
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=1546203216.36639d91c3ffede7e52fae2205b78507c458fd7d.gyakovlev@gentoo \
--to=gyakovlev@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