Github messages for voidlinux
 help / color / mirror / Atom feed
From: fanyx <fanyx@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: kubectx-0.9.4
Date: Wed, 12 Oct 2022 12:12:43 +0200	[thread overview]
Message-ID: <20221012101243.q6utF1jjrzmdVC1kXnK3B6Mdal5EWYP66BVZBFKTB4k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39732@inbox.vuxu.org>

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

There is an updated pull request by fanyx against master on the void-packages repository

https://github.com/fanyx/void-packages kubectx
https://github.com/void-linux/void-packages/pull/39732

New package: kubectx-0.9.4
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->

#### Local build testing
- I built this PR locally for my native architecture, x86_64

New PR for previously abandoned package.
https://github.com/void-linux/void-packages/pull/17088

I'll maintain updates if necessary.

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

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

From b46f6f2856be985f185bfd246540d32aa5e728ec Mon Sep 17 00:00:00 2001
From: fanyx <fanyx@fanyx.xyz>
Date: Wed, 12 Oct 2022 12:12:28 +0200
Subject: [PATCH] New package: kubectx-0.9.4

---
 srcpkgs/kubectx/patches/version.patch | 26 ++++++++++++++++++++++++
 srcpkgs/kubectx/template              | 29 +++++++++++++++++++++++++++
 2 files changed, 55 insertions(+)
 create mode 100644 srcpkgs/kubectx/patches/version.patch
 create mode 100644 srcpkgs/kubectx/template

diff --git a/srcpkgs/kubectx/patches/version.patch b/srcpkgs/kubectx/patches/version.patch
new file mode 100644
index 000000000000..a92c90878368
--- /dev/null
+++ b/srcpkgs/kubectx/patches/version.patch
@@ -0,0 +1,26 @@
+diff --git a/cmd/kubectx/version.go b/cmd/kubectx/version.go
+index 964f334..5b924da 100644
+--- a/cmd/kubectx/version.go
++++ b/cmd/kubectx/version.go
+@@ -8,7 +8,7 @@ import (
+ )
+ 
+ var (
+-	version = "v0.0.0+unknown" // populated by goreleaser
++	version = "v0.9.4" // patched for xbps
+ )
+ 
+ // VersionOps describes printing version string.
+diff --git a/cmd/kubens/version.go b/cmd/kubens/version.go
+index 964f334..5b924da 100644
+--- a/cmd/kubens/version.go
++++ b/cmd/kubens/version.go
+@@ -8,7 +8,7 @@ import (
+ )
+ 
+ var (
+-	version = "v0.0.0+unknown" // populated by goreleaser
++	version = "v0.9.4" // patched for xbps
+ )
+ 
+ // VersionOps describes printing version string.
diff --git a/srcpkgs/kubectx/template b/srcpkgs/kubectx/template
new file mode 100644
index 000000000000..b50b72e8221c
--- /dev/null
+++ b/srcpkgs/kubectx/template
@@ -0,0 +1,29 @@
+# Template file for 'kubectx'
+pkgname=kubectx
+version=0.9.4
+revision=1
+# build_style=go
+# go_import_path="github.com/ahmetb/kubectx"
+makedepends="go"
+depends="fzf kubectl"
+short_desc="Faster way to switch between clusters and namespaces in kubectl"
+maintainer="fanyx <fanyx@fanyx.xyz>"
+license="Apache-2.0"
+homepage="https://github.com/ahmetb/kubectx"
+distfiles="https://github.com/ahmetb/kubectx/archive/v${version}.tar.gz"
+checksum=91e6b2e0501bc581f006322d621adad928ea3bd3d8df6612334804b93efd258c
+nopie=y
+
+do_build() {
+	go build -o bin/kubectx ./cmd/kubectx
+	go build -o bin/kubens ./cmd/kubens
+}
+
+do_install() {
+	for bin in kubectx kubens; do
+		vbin bin/$bin $bin
+		for sh in bash zsh fish; do
+			vcompletion completion/$bin.$sh $sh $sh $bin
+		done
+	done
+}

  parent reply	other threads:[~2022-10-12 10:12 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05  9:17 [PR PATCH] " fanyx
2022-10-05  9:20 ` [PR PATCH] [Updated] " fanyx
2022-10-05  9:23 ` fanyx
2022-10-05  9:59 ` [PR REVIEW] " classabbyamp
2022-10-05 10:00 ` classabbyamp
2022-10-05 10:04 ` classabbyamp
2022-10-05 10:04 ` classabbyamp
2022-10-05 10:10 ` fanyx
2022-10-12  9:20 ` [PR PATCH] [Updated] " fanyx
2022-10-12  9:23 ` fanyx
2022-10-12  9:32 ` fanyx
2022-10-12  9:33 ` classabbyamp
2022-10-12  9:34 ` fanyx
2022-10-12  9:39 ` classabbyamp
2022-10-12  9:55 ` [PR REVIEW] " paper42
2022-10-12 10:00 ` fanyx
2022-10-12 10:12 ` fanyx [this message]
2022-10-12 11:49 ` paper42
2022-10-12 12:02 ` fanyx
2022-10-12 12:11 ` [PR PATCH] [Updated] " fanyx
2022-10-12 12:20 ` fanyx
2022-10-12 12:23 ` paper42
2022-10-12 12:30 ` fanyx
2022-10-12 12:39 ` [PR PATCH] [Updated] " fanyx
2022-10-12 12:45 ` fanyx
2022-10-17  7:01 ` [PR PATCH] [Updated] " fanyx
2022-10-17  7:06 ` fanyx
2023-01-16  1:59 ` github-actions
2023-01-16 13:00 ` fanyx
2023-01-16 13:00 ` [PR PATCH] [Closed]: " fanyx
2023-01-16 13:00 ` fanyx

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=20221012101243.q6utF1jjrzmdVC1kXnK3B6Mdal5EWYP66BVZBFKTB4k@z \
    --to=fanyx@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).