Overview
Request 614593 superseded
- Ensure neutrality of description. Use noun phrase for summary.
- Update to 0.27.0
- Update to 0.26.1
- Fix Makefile to build for architectures different than AMD64
- Update to 0.22.3
- Update to 0.19.1
- Update to 0.17.1
- update to 0.16.0
- Add update-suse-docker-machine-provisioner.patch patch: required
to use latest SUSE/openSUSE provisioner of docker-machine
- Split the localkube into a dedicated sub-package
- initial package for 0.11.0
- Created by mrostecki
- In state superseded
- Supersedes 614507
- Superseded by 615019
-
Open review for
legal-auto
-
Open review for
opensuse-review-team
- Open review for openSUSE:Factory:Staging:adi:30
Request History
mrostecki created request
- Ensure neutrality of description. Use noun phrase for summary.
- Update to 0.27.0
- Update to 0.26.1
- Fix Makefile to build for architectures different than AMD64
- Update to 0.22.3
- Update to 0.19.1
- Update to 0.17.1
- update to 0.16.0
- Add update-suse-docker-machine-provisioner.patch patch: required
to use latest SUSE/openSUSE provisioner of docker-machine
- Split the localkube into a dedicated sub-package
- initial package for 0.11.0
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto added repo-checker as a reviewer
Please review build success
factory-auto accepted review
Check script succeeded
staging-bot added openSUSE:Factory:Staging:adi:30 as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:30"
staging-bot accepted review
Picked openSUSE:Factory:Staging:adi:30
repo-checker accepted review
cycle and install check passed
https://en.opensuse.org/openSUSE:Creating_a_changes_file_(RPM) This should be a bit more verbose beyond a version bump.
Why should we be shipping statitcally linked binaries ? e.g. minikube-rpmlintrc Can this be dropped ?
Static linking is de facto a standard in Go language, because the most of Go programs (including minikube) are bundling dependencies in vendor/ directory inside their source tree. That's why dynamic linking doesn't make much sense there. Also, dynamic linking in Go is quite experimental and not recommended.
All the Go programs are statically linked. There's nothing we can do, that's one of the "features" of the language itself.
OK, thanks for the explanation.