Search Criteria
Package Details: skaffold 0.23.0-1
Git Clone URL: | https://aur.archlinux.org/skaffold.git (read-only) |
---|---|
Package Base: | skaffold |
Description: | A command line tool that facilitates continuous development for Kubernetes applications |
Upstream URL: | https://github.com/GoogleContainerTools/skaffold |
Licenses: | |
Submitter: | frealgagu |
Maintainer: | frealgagu (maximbaz) |
Last Packager: | frealgagu |
Votes: | 7 |
Popularity: | 1.316301 |
First Submitted: | 2018-04-19 00:02 |
Last Updated: | 2019-02-15 16:14 |
Dependencies (5)
- docker (docker-experimental-git, docker-git-x86, docker-git, docker-stable-bin, docker-bin)
- kubectl-bin (kubectl-beta-bin)
- go-pie (make)
- google-cloud-sdk (optional) – To use GKE
- minikube (minikube-git, minikube-bin) (optional) – To use Minikube
Latest Comments
1 2 Next › Last »
stefanc_diff commented on 2018-12-07 21:39
Indeed the
_upstream_pkgname
was a copy/paste mistake.Thanks for accepting my contribution ! Keep up the good packaging work !
frealgagu commented on 2018-12-07 12:42
@stefanc_diff I had tried download the files based on the .SRCINFO, but the URL wasn't complete, I suppose the _upstream_pkgname variable was not defined.
I'll include the files in a moment. Thanks for your contribution.
stefanc_diff commented on 2018-12-07 11:14
@maximbaz Thanks for verifying access to the docs !
${_upstream_pkgname} variable This is a common variable I use in my PKGBUILDs to separate the arch/AUR pkg name ( denoted by
${pkgname}` from the upstream pkg name denoted by the variable above.This helps with packaging when the
${pkgname}
needed by AUR/arch pkg system would beskaffold-bin
(as an example) but the upstream pkg name isskaffold
For this pkg though
${_upstream_pkgname}
==${pkgname}
The "cleanup the package() phase a bit" phrase This refers to using the 4
install
commands in the package() phase instead ofcp
andchmod
commandsmaximbaz commented on 2018-12-05 22:02
Sharing the patch in comments or gist is totally fine. I confirm that the links are accessible, html and pdf open fine for me.
frealgagu, I'm fine adding these to /usr/share/doc as proposed, let me know if you also agree and I can do it (or just do it yourself ;)). Agree about LICENSE not being necessary to include.
stefanc_diff, I'm only not sure where does the variable
${_upstream_pkgname}
come from in your patch, I assume you wanted to use${pkgname}
here. Also not sure to which change in your patch the phrase "cleanup the package() phase a bit" refers to :)stefanc_diff commented on 2018-12-05 21:54
@frealgagu
1) Please have a look again in the patch I've sent ( variables _doc_html && _doc_pdf ) and you'll be able to see that these are openly available , no login necessary. When I test PKGBUILDs I always test them in a clean chroot using the arch devtools pkg. If these docs where behind some login page my builds wouldn't build, but my builds are running, retrieving the docs and building fine. These docs are useful to have offline/on_workstation since skaffold is not the easiest tool to grasp, being also a very new tool.
2) I comprehend your point about the LICENSE, that was the least important file in the git patch.
How do you think it is best to get this patch in ?
frealgagu commented on 2018-12-05 18:03
@stefanc_diff you need to be logged in to storage.googleapis.com in order to be able to download the docs, so it's not something you can add to a PKGBUILD. LICENSE file is not necessary to be included in license files because that is Apache and not a custom license.
stefanc_diff commented on 2018-12-05 16:01
@frealgagu @maximbaz I have a patch for this package to add docs to the pkg and cleanup the package() phase a bit. How do you want to get this patch in ? - patch file - content of the patch file in the comments - commit to repo
I've tried the last option, but I can only clone the repo not push back to it. Do I need to be added on the comaintainer list for this package to be able to push to it?
Just in case the comaintainer thing is too complicated here is the git patch for these changes I was mentioning
maximbaz commented on 2018-11-30 18:10
I see, thanks! I also noticed you added a patch for this, did you submit it upstream?
frealgagu commented on 2018-11-30 14:45
@maximbaz it shows in verbose mode
if you leave it without version number it will try to take it via "git reve-parse HEAD" but if you are not in a valid git repository (or you don't have git installed) it shows error. Even worse, if you clone the aur repository to install it, it shows the aur git number which is incorrect.
maximbaz commented on 2018-11-30 14:04
frealgagu what's the point of specifying commit? It doesn't show up in
skaffold version
anyway, so I'm not sure.