@zer0def
Of course not, especially with that nice patch attached! Thanks for the help, 1.7.0-3 contains arm and aarch releases :)
Git Clone URL: | https://aur.archlinux.org/rancher-k3d-bin.git (read-only, click to copy) |
---|---|
Package Base: | rancher-k3d-bin |
Description: | Little helper to run Rancher Labs k3s in Docker |
Upstream URL: | https://github.com/rancher/k3d |
Keywords: | docker k3d k3s k8s kubernetes rancher |
Licenses: | |
Conflicts: | |
Provides: | |
Submitter: | JohnnyCrazy |
Maintainer: | JohnnyCrazy (k3d, sp0-deploy) |
Last Packager: | k3d |
Votes: | 8 |
Popularity: | 0.63 |
First Submitted: | 2019-09-14 23:04 |
Last Updated: | 2021-01-20 14:37 |
@zer0def
Of course not, especially with that nice patch attached! Thanks for the help, 1.7.0-3 contains arm and aarch releases :)
Hey Johnny, would it be much of a bother to add support for other architectures?: https://github.com/zer0def/PKGBUILDs/commit/1e3d7bc99a610115a4a7d17db9d571668a7fc747.patch
This package only contains the stable release of rancher's k3d
.
If you're intereseted in pre-release/beta versions, head over to rancher-k3d-beta-bin
I'm not sure if we should update the package to pre release versions, will do some research on how to handle this on the aur normally.
Here's a patch for 3.0.0-rc0
index b08cfdd..cddb653 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,14 +1,14 @@
# Maintainer: Jonas Dellinger <jonas@dellinger.dev>
pkgname="rancher-k3d-bin"
-pkgver=1.7.0
+pkgver='3.0.0_rc.0'
pkgrel=1
pkgdesc='Little helper to run Rancher Labs k3s in Docker'
arch=('x86_64')
url='https://github.com/rancher/k3d'
license=('MIT')
provides=("k3d")
-source=("${pkgname}-${pkgver}::https://github.com/rancher/k3d/releases/download/v$pkgver/k3d-linux-amd64")
-sha256sums=('da9ff31bcf4377fadfb065f4998d347f19de1168a5a553ce2c23b763ee1f6098')
+source=("${pkgname}-${pkgver}::https://github.com/rancher/k3d/releases/download/v${pkgver/_/-}/k3d-linux-amd64")
+sha256sums=('7564c701eecbba57622f2df833ed393b60affbf36281f6cb2f219efb1be78646')
package() {
install -Dm 0755 ${pkgname}-${pkgver} "$pkgdir/usr/bin/k3d"
@dg10a
I'm fairly new to the AUR, so correct me if I'm wrong. I decided to keep the original binary name k3d
because that's what the upstream package is called. I'm not sure if it is common to rename the binaries of upstream packages? Do we have some example where this is done?
This package provides k3d, which is a different program entirely
I think we already have a lot of programs which have name clashes. Even your linked k3d has a wrong package name IMO, it should be k-3d
.
This package provides k3d
, which is a different program entirely. The provided package should be renamed to rancher-k3d
.
https://aur.archlinux.org/packages/k3d/ http://www.k-3d.org/
@srueg Seems like you're correct. Weird tho, I was pretty sure I correctly replaced it. Maybe they updated the binary afterwards...IDK. 1.3.4-2 fixes it.
Wrong sha256? I get: 41e0579b1499f6051e9d0d8a6d39d5f419e1037851c0121b676190af5825f4c0
Pinned Comments
JohnnyCrazy commented on 2020-06-04 09:18
This package only contains the stable release of rancher's
k3d
.If you're intereseted in pre-release/beta versions, head over to rancher-k3d-beta-bin