From: dataCobra <dataCobra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] vagrant: update to 2.3.0.
Date: Tue, 23 Aug 2022 10:08:43 +0200 [thread overview]
Message-ID: <20220823080843.zUelhxM_PskBrvL6i2UNY9XEpvExJvHM9zjH3yCjwXY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38852@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
There is an updated pull request by dataCobra against master on the void-packages repository
https://github.com/dataCobra/void-packages vagrant-update-2.3.0
https://github.com/void-linux/void-packages/pull/38852
vagrant: update to 2.3.0.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64)
I've also updated `do_install` process to add the completion for bash and zsh. A ftplugin for
vim is also available and will now be installed.
I've added a patch to get rid of an annoying message when executing vagrant commands.
A patch file from https://github.com/void-linux/void-packages/pull/38852.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-vagrant-update-2.3.0-38852.patch --]
[-- Type: text/x-diff, Size: 3208 bytes --]
From 9ba4cf6a7396cccadb8938ac6f716a818ee30f56 Mon Sep 17 00:00:00 2001
From: dataCobra <datacobra@thinkbot.de>
Date: Tue, 23 Aug 2022 10:08:10 +0200
Subject: [PATCH] vagrant: update to 2.3.0.
---
.../silence-warning-about-installer.patch | 15 +++++++++++
srcpkgs/vagrant/template | 26 +++++++++++--------
2 files changed, 30 insertions(+), 11 deletions(-)
create mode 100644 srcpkgs/vagrant/patches/silence-warning-about-installer.patch
diff --git a/srcpkgs/vagrant/patches/silence-warning-about-installer.patch b/srcpkgs/vagrant/patches/silence-warning-about-installer.patch
new file mode 100644
index 000000000000..4432a13d3737
--- /dev/null
+++ b/srcpkgs/vagrant/patches/silence-warning-about-installer.patch
@@ -0,0 +1,15 @@
+--- /bin/vagrant 2022-08-06 00:16:44.000000000 +0200
++++ /bin/vagrant 2022-08-23 09:50:50.613805575 +0200
+@@ -221,11 +221,6 @@
+ end
+ end
+
+- if !Vagrant.in_installer? && !Vagrant.very_quiet?
+- # If we're not in the installer, warn.
+- env.ui.warn(I18n.t("vagrant.general.not_in_installer") + "\n", prefix: false)
+- end
+-
+ # Acceptable experimental flag values include:
+ #
+ # Unset - Disables experimental features
+
diff --git a/srcpkgs/vagrant/template b/srcpkgs/vagrant/template
index f15d85850d03..a9cc015e4fe8 100644
--- a/srcpkgs/vagrant/template
+++ b/srcpkgs/vagrant/template
@@ -1,7 +1,7 @@
# Template file for 'vagrant'
pkgname=vagrant
-version=2.2.19
-revision=2
+version=2.3.0
+revision=1
archs="i686 x86_64*"
hostmakedepends="ruby"
makedepends="ruby-devel zlib-devel"
@@ -10,8 +10,9 @@ short_desc="Tool for building and distributing development environments"
maintainer="Andrea Brancaleoni <abc@pompel.me>"
license="MIT"
homepage="https://www.vagrantup.com/"
-distfiles="https://github.com/mitchellh/${pkgname}/archive/v${version}.tar.gz"
-checksum=4f0e6b1d466e26dead682c4d4843e8f64a012eba4be91506ae6c6d34d3d9c8f9
+changelog="https://github.com/hashicorp/${pkgname}/blob/v${version}/CHANGELOG.md"
+distfiles="https://github.com/hashicorp/${pkgname}/archive/v${version}.tar.gz"
+checksum=1931dbf29ec3c6622a649ae145fe706e5b957d7075870ce577358dd22c3d5dca
nocross=yes
post_extract() {
@@ -25,6 +26,16 @@ do_build() {
do_install() {
GEM_PATH=$DESTDIR/usr/lib/$pkgname GEM_HOME="$GEM_PATH" gem install $pkgname-$version.gem --no-document -- --disable-clean
+ vlicense LICENSE
+
+ vmkdir usr/bin
+ vbin $FILESDIR/$pkgname
+
+ vcompletion "contrib/bash/completion.sh" bash
+
+ mkdir -p /usr/share/vim/vim90/ftplugin/
+ cp contrib/vim/vagrantfile.vim /usr/share/vim/vim90/ftplugin/
+
find ${DESTDIR} -type f -name \*.a -delete
find ${DESTDIR} -type f -name \*.log -delete
find ${DESTDIR} -type f -name \*.c -delete
@@ -49,11 +60,4 @@ do_install() {
find ${DESTDIR} -type d -name doc -print0|xargs -0 rm -rf --
find ${DESTDIR} -type d -name ports -print0|xargs -0 rm -rf --
rm -r ${DESTDIR}/usr/lib/$pkgname/cache
-
- vmkdir usr/bin
- vmkdir usr/share/bash-completion/completions
- vbin $FILESDIR/$pkgname
- ln -sf /usr/lib/$pkgname/gems/$pkgname-$version/contrib/bash/completion.sh \
- $DESTDIR/usr/share/bash-completion/completions/$pkgname
- vlicense LICENSE
}
next prev parent reply other threads:[~2022-08-23 8:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 8:04 [PR PATCH] " dataCobra
2022-08-23 8:08 ` dataCobra [this message]
2022-08-25 17:55 ` [PR REVIEW] " classabbyamp
2022-08-25 17:55 ` classabbyamp
2022-08-25 17:55 ` classabbyamp
2022-08-25 17:55 ` classabbyamp
2022-08-25 17:55 ` classabbyamp
2022-08-25 19:23 ` dataCobra
2022-08-25 19:41 ` classabbyamp
2022-08-26 6:22 ` [PR PATCH] [Updated] " dataCobra
2022-08-26 6:23 ` [PR REVIEW] " dataCobra
2022-08-26 6:24 ` [PR PATCH] [Updated] " dataCobra
2022-08-26 6:26 ` dataCobra
2022-08-26 7:24 ` [PR REVIEW] " classabbyamp
2022-08-26 7:24 ` classabbyamp
2022-08-26 7:24 ` classabbyamp
2022-08-26 7:25 ` classabbyamp
2022-08-26 7:45 ` [PR PATCH] [Updated] " dataCobra
2022-08-26 7:45 ` [PR REVIEW] " dataCobra
2022-08-26 7:45 ` dataCobra
2022-08-26 7:47 ` dataCobra
2022-08-29 10:26 ` dataCobra
2022-08-29 16:44 ` classabbyamp
2022-08-29 21:06 ` [PR PATCH] [Merged]: " classabbyamp
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=20220823080843.zUelhxM_PskBrvL6i2UNY9XEpvExJvHM9zjH3yCjwXY@z \
--to=datacobra@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).