Github messages for voidlinux
 help / color / mirror / Atom feed
From: Vaelatern <Vaelatern@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] vault: enable UI build by default
Date: Mon, 20 Mar 2023 18:42:25 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42884@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 514 bytes --]

There is a new pull request by Vaelatern against master on the void-packages repository

https://github.com/Vaelatern/void-packages vault-ui
https://github.com/void-linux/void-packages/pull/42884

vault: enable UI build by default
@the-maldridge I got this working, do we want it enabled by default like upstream?

I checked for a distfile that had the assets already built, would welcome someone finding such a tarball.

A patch file from https://github.com/void-linux/void-packages/pull/42884.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-vault-ui-42884.patch --]
[-- Type: text/x-diff, Size: 1460 bytes --]

From 85169c650ad278a70c4fa78ae6f1e21ac31f582a Mon Sep 17 00:00:00 2001
From: Toyam Cox <Vaelatern@voidlinux.org>
Date: Mon, 20 Mar 2023 13:41:22 -0400
Subject: [PATCH] vault: enable UI build by default

---
 srcpkgs/vault/template | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/vault/template b/srcpkgs/vault/template
index 28bff52ec6f0..04d6bd3da931 100644
--- a/srcpkgs/vault/template
+++ b/srcpkgs/vault/template
@@ -1,12 +1,13 @@
 # Template file for 'vault'
 pkgname=vault
 version=1.13.0
-revision=1
+revision=2
 build_style=go
 go_import_path="github.com/hashicorp/vault"
-go_build_tags="release"
+go_build_tags="release $(vopt_if ui ui)"
 _git_commit=a4cf0dc4437de35fce4860857b64569d092a9b5a
 go_ldflags="-X ${go_import_path}/sdk/version.GitCommit=${_git_commit}"
+hostmakedepends="$(vopt_if ui yarn)"
 depends="libcap-progs"
 short_desc="Manage Secrets and Protect Sensitive Data"
 maintainer="Michael Aldridge <maldridge@voidlinux.org>"
@@ -17,11 +18,19 @@ checksum=ebffe482b9e23346862272fbab7d589315200f2004b63b26b2df43823a5d3fb6
 system_accounts="_vault"
 make_dirs="/var/lib/vault 0700 _vault _vault
  /etc/vault 0750 root _vault"
+build_options="ui"
+build_options_default="ui"
 
 case "$XBPS_TARGET_MACHINE" in
 	arm*) go_ldflags="$go_ldflags -linkmode=external";;
 esac
 
+pre_build() {
+	if [ "$build_option_ui" ]; then
+		make static-dist
+	fi
+}
+
 post_install() {
 	vlicense LICENSE
 	vsv vault

             reply	other threads:[~2023-03-20 17:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 17:42 Vaelatern [this message]
2023-03-20 18:00 ` the-maldridge
2023-06-19  1:59 ` github-actions
2023-06-19 16:04 ` [PR PATCH] [Closed]: " Vaelatern

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42884@inbox.vuxu.org \
    --to=vaelatern@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).