Arch Linux User Repository

@zhiwei go and git are make dependencies and required to build the package. See build() in PKGBUILD

kubectl is exec'd from Go code. I did not check the last versions if this is still the case for the local machine or if it's only happening on the created nodes. (Yet)

Edit: I definitely missed at least one thing related to git use in build(). I'll look into it and push and update if it turns out I can drop the dependency.

Why does it depend on kubectl, git and go?

That makes more sense ofc, thanks for clarifying

No, Docker 20.10.0+ is now required, with no change for Podman.

As in, if your version of docker is older than that, you're going to have a bad time.

moved docker back to optdepends.
According to the release note of v0.20.0, docker is now required.

Please check if everything still works for you without docker.

Please can we remove the dependency on docker, it should be optional, as with podman

@thurstylark kind supports podman without the need to have a docker executable or wrapper. The choice is between docker and podman which can be installed side-by-side. Forcing the user to choose between docker an podman-docker would suggest it's either or. But I see your point and I'll think about it. I feel like I had already played around with kind + podman-dnsname and ended up choosing not to include it. Hope I'll be able to remember the reason for my decision.

Because podman-docker provides docker and depends on podman, it should now be sufficient to move docker to the depends array, and remove podman from the optdepends array. When a user installs this package, but does not have either docker or podman installed, pacman will ask the user to pick one from a list of packages that provide docker, and podman-docker will be in that list. (this is something that has been set up by the maintainer of podman-docker, and may not have been the case when this was being discussed a year ago)

As for podman-dnsname, I would suggest adding that to the optdepends array with a comment along the lines of "required when using podman in place of docker". podman-dnsname has a hard dep on dnsmasq, so you shouldn't need to mention dnsmasq (also something that might have changed since this was discussed)

Since users are shown a list of optdepends and their comments in pacman's output, I think both of these changes should be all you need to communicate what's necessary to the user.

@matthias.lisin I'm not familiar with the PKG syntax for complex dependencies, so can't suggest anything about it. The only thing I can think about is explaining the situation in a message at the end of the installation process and leave the installation up to the user. Anyway, KinD is quite of a niche software, so I hope users will understand the situation and the need of a container engine in the host.

@miguescri I kinda jumped the gun on podman tbh. Couldn't properly communicate in the PKGBUILD that you need either docker or podman, podman-dnsname and dnsmasq. Not quiet sure myself why I chose that route.

I'll put the podman packages back in optdepends, and also keep docker there. Gonna look a bit ugly because those two packages don't have a common provides to trigger a XOR choice when installing kind. Although podman needs podman-dnsname, and podman-dnsname needs dnsmasq, their depends doesn't reflect that. It will look a bit messy.

I appreciate any suggestions on how to handle this.