Skip to content
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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lab: generate and install zsh completion #57842

Merged
merged 2 commits into from Mar 20, 2019

Conversation

dtzWill
Copy link
Member

@dtzWill dtzWill commented Mar 18, 2019

Motivation for this change

zsh completion! :)

Env variables are set to dummy values
so lab doesn't get stuck trying to helpfully
interact with user for initial configuration.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@dtzWill
Copy link
Member Author

dtzWill commented Mar 18, 2019 via email

@worldofpeace
Copy link
Contributor

Oh! Ha, well this is because I forgot to upstream porting lab over to the new buildGoModule goodness. Which apparently has different behavior re:outputs?

Hmm, I wasn't aware of buildGoModule (so many happenings in nixpkgs) but I'm presently surprised 😄

@kalbasit Any reason why the outputs for buildGoModule are firstly out wherein buildGoPackage it was bin?

@dtzWill
Copy link
Member Author

dtzWill commented Mar 18, 2019

@kalbasit Any reason why the outputs for buildGoModule are firstly out wherein buildGoPackage it was bin?

It seems it's more that buildGoModule has a single output by default ("out"), where buildGoPackage would have two -- which I'm sure there's a reason for but I don't know it :). May be good to sort this out or make them consistent, dunno.

Anyway, merging this as it should be ready now!

@dtzWill
Copy link
Member Author

dtzWill commented Mar 18, 2019

Just kidding, hashes are wrong? They might depend on something I have changed, will check sorry.

@worldofpeace
Copy link
Contributor

Weird they're still wrong. 😕

@kalbasit
Copy link
Member

@kalbasit Any reason why the outputs for buildGoModule are firstly out wherein buildGoPackage it was bin?

The initial version of buildGoModule had both the $bin and the $out outputs. However, @Mic92 pointed out that all of the buildGoPackage derivations had a useful output ($bin) and a rather empty and useless output $out and he was unable to consolidate both due to all packages (and possibly outside nixpkgs) usage of buildGoPackage. Since buildGoModule was a new infrastructure, we wanted to consolidate the outputs.

Hmm, I wasn't aware of buildGoModule (so many happenings in nixpkgs) but I'm presently surprised

https://kalbas.it/2019/03/17/announcing-the-new-golang-infrastructure-buildgomodule/ :)

@worldofpeace
Copy link
Contributor

The initial version of buildGoModule had both the $bin and the $out outputs. However, @Mic92 pointed out that all of the buildGoPackage derivations had a useful output ($bin) and a rather empty and useless output $out and he was unable to consolidate both due to all packages (and possibly outside nixpkgs) usage of buildGoPackage. Since buildGoModule was a new infrastructure, we wanted to consolidate the outputs.

Right, all outputs should provide some sort of use. Think you made the correct decision there.

https://kalbas.it/2019/03/17/announcing-the-new-golang-infrastructure-buildgomodule/ :)

Nice writeup 👍 Thank you for your contributions to the Golang infrastructure.

goDeps = ./deps.nix;
subPackages = [ "." ];

modSha256 = "0bw47dd1b46ywsian2b957a4ipm77ncidipzri9ra39paqlv7abb";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
modSha256 = "0bw47dd1b46ywsian2b957a4ipm77ncidipzri9ra39paqlv7abb";
modSha256 = "1g72fnkibmdd9i20wgp5fjf556xp2xwan06dmn3f5rkmnicy3ccl";

as reported by ofborg.

Env variables are set to dummy values
so `lab` doesn't get stuck trying to helpfully
interact with user for initial configuration.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants