From: nilium <nilium@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] tailscale: update to 0.100.0.
Date: Thu, 23 Jul 2020 17:58:19 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23766@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 505 bytes --]
There is a new pull request by nilium against master on the void-packages repository
https://github.com/nilium/ecks-bops-packages tailscale
https://github.com/void-linux/void-packages/pull/23766
tailscale: update to 0.100.0.
Because tailscale uses a -$RELEASE suffix on versions and xbps-src
doesn't allow that, there's an additional _release variable that acts
as the release suffix for wrksrc and distfiles.
A patch file from https://github.com/void-linux/void-packages/pull/23766.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-tailscale-23766.patch --]
[-- Type: text/x-diff, Size: 1483 bytes --]
From 28abf1d03838c237c9c573d484357b9edecc8ab4 Mon Sep 17 00:00:00 2001
From: Noel Cower <ncower@nil.dev>
Date: Thu, 23 Jul 2020 08:47:28 -0700
Subject: [PATCH] tailscale: update to 0.100.0.
Because tailscale uses a -$RELEASE suffix on versions and xbps-src
doesn't allow that, there's an additional _release variable that acts
as the release suffix for wrksrc and distfiles.
---
srcpkgs/tailscale/template | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/tailscale/template b/srcpkgs/tailscale/template
index b7b7ad1f986..074fcf94f0f 100644
--- a/srcpkgs/tailscale/template
+++ b/srcpkgs/tailscale/template
@@ -1,7 +1,9 @@
# Template file for 'tailscale'
pkgname=tailscale
-version=0.99.1
+version=0.100.0
revision=1
+_release=-153
+wrksrc="${pkgname}-${version}${_release}"
build_style=go
go_import_path="tailscale.com"
go_package="tailscale.com/cmd/tailscale tailscale.com/cmd/tailscaled"
@@ -11,8 +13,8 @@ short_desc="Easy, secure, cross platform WireGuard, oauth2, and 2FA/SSO"
maintainer="Noel Cower <ncower@nil.dev>"
license="BSD-3-Clause"
homepage="https://tailscale.com"
-distfiles="https://github.com/tailscale/tailscale/archive/v${version}.tar.gz"
-checksum=9d124c6ade7fe4bc599259ee77e21fa6c044828c87d4290020b2c9cce2371ba5
+distfiles="https://github.com/tailscale/tailscale/archive/v${version}${_release}.tar.gz"
+checksum=e055b72ea20d1288eae61fc0fd1a0108847891e651729d8b3cd318066633ed86
post_install() {
vlicense LICENSE
next reply other threads:[~2020-07-23 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 15:58 nilium [this message]
2020-07-23 16:17 ` ericonr
2020-07-23 18:52 ` nilium
2020-07-25 5:53 ` [PR PATCH] [Merged]: " jnbr
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-23766@inbox.vuxu.org \
--to=nilium@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).