New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
kube3d: increase discoverability #99563
Conversation
0d6c1f3
to
3461263
Compare
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: |
3461263
to
9b58a5a
Compare
/marvin opt-in |
Hi! I'm an experimental bot. My goal is to guide this PR through its stages, hopefully ending with a merge. You can read up on the usage here. |
Result of 1 package built:
|
@06kellyjac thanks for the PR, I like your changes, but I have 2 questions:
About the first question, I found this related issue: #99200 but I still don't understand the reason. I'm not opposed to do that changes, I just want to understand the motivation behind them |
IMO it makes more sense for me that something called an "Array" actually be an array. I'm not sure if there are any other advantages or disadvantages that are more substantial. 位 BOB=("a" "b" "c")
位 echo "${BOB[@]}"
a b c 位 BUILDFLAGSARRAY=("-tags" "netgo" "-ldflags='-w -X PACKAGE.gitTag=VERSION'")
位 echo "${BUILDFLAGSARRAY[@]}" # notwrapped in 'quotes'
-tags netgo -ldflags='-w -X PACKAGE.gitTag=VERSION'
If |
Totally agree with that, it's only that in the examples I remember, it was always a string. And if it ain't broke, don't fix it.
It makes sense to me, I only wanted to know if there are some best practices about it. To me, it's ok to merge your changes, I just wanted to know if there are some guide lines about that topics |
Thanks for looking it all over
No worries. I've not been using and packaging for nix too long so I'm also trying to work out some of the best practices 馃槄 |
Reminder: Please review! This Pull Request is awaiting review. If you are the assigned reviewer, please have a look. Try to find another reviewer if necessary. If you can't, please say so. If the status is not accurate, please change it. If nothing happens, this PR will be put back in the |
I tested the executable and all looks good. |
homepage = "https://github.com/rancher/k3d"; | ||
description = "A helper to run k3s (Lightweight Kubernetes. 5 less than k8s) in a docker container"; | ||
description = "A helper to run k3s (Lightweight Kubernetes. 5 less than k8s) in a docker container - k3d"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
description = "A helper to run k3s (Lightweight Kubernetes. 5 less than k8s) in a docker container - k3d"; | |
description = "A helper to run k3s (Lightweight Kubernetes. 5 less than k8s) in a docker container"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added k3d to the short description because nix search
uses description
but doesn't look at longDescription
nix search
seems to only look at the short description so it's worth
including there too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is fine with me. Sound good to leave it @SuperSandro2000?
homepage = "https://github.com/rancher/k3d"; | ||
description = "A helper to run k3s (Lightweight Kubernetes. 5 less than k8s) in a docker container"; | ||
description = "A helper to run k3s (Lightweight Kubernetes. 5 less than k8s) in a docker container - k3d"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is fine with me. Sound good to leave it @SuperSandro2000?
Can you please resolve the merge conflict? |
search.nixos.org was able to show me `deno` when searching for "executable" which was in the longDescription
While I was able to find `deno` by searching for "executable" from it's longDescription on search.nixos.org, I couldn't find it using `nix search` `nix search` seems to only look at the short description so it's worth including there too.
Moved k3sVersion to be a variable. Converted buildFlagsArray to an array Moved vendorSha256 closer to src Moved doCheck between build and install related bits (like where the phase happens) Replaced stdenv.lib with lib
9b58a5a
to
cdfa9b0
Compare
Done |
Motivation for this change
I've searched for "k3d" previously using https://search.nixos.org but
kube3d
didn't show up so I've been maitaining my own copy of it for months 馃槄Mentioning "k3d" in the
description
andlongDescription
should make it easier to find.Things done
nixpkgs-fmt
ed the file to fit with contributing guidelines.Mentioned
k3d
in thedescription
andlongDescription
https://search.nixos.org can find things from either description but
nix search
just looks at the short description.sandbox
innix.conf
on non-NixOS linux)[ ] macOSNot on the platforms listnix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)