Skip to content

Comments

closure-size: nix-serve: include bzip2 on PATH#12771

Closed
ttuegel wants to merge 1 commit intoNixOS:closure-sizefrom
ttuegel:closure-size-nix-serve
Closed

closure-size: nix-serve: include bzip2 on PATH#12771
ttuegel wants to merge 1 commit intoNixOS:closure-sizefrom
ttuegel:closure-size-nix-serve

Conversation

@ttuegel
Copy link
Member

@ttuegel ttuegel commented Feb 2, 2016

This fixes nix-serve on the closure-size branch.

/cc @vcunat

@ttuegel ttuegel added 0.kind: bug Something is broken 6.topic: closure size The final size of a derivation, including its dependencies labels Feb 2, 2016
@mention-bot
Copy link

By analyzing the blame information on this pull request, we identified @edolstra and @wkennington to be potential reviewers

@dezgeg
Copy link
Contributor

dezgeg commented Feb 2, 2016

Actually bzip2 should be coming from here: https://github.com/NixOS/nixpkgs/blob/closure-size/nixos/modules/services/networking/nix-serve.nix#L53. Which means we should do the output selection thing in systemd.services.<foo>.path as well.

@ttuegel
Copy link
Member Author

ttuegel commented Feb 2, 2016

@dezgeg Thanks! We'll do that in another PR. Closing this one.

@ttuegel ttuegel closed this Feb 2, 2016
@ttuegel ttuegel deleted the closure-size-nix-serve branch February 2, 2016 15:26
@edolstra
Copy link
Member

edolstra commented Feb 2, 2016

Well, arguably it's cleaner to fix it in the wrapper script than in the systemd service, since the latter makes it work for all users.

@ttuegel
Copy link
Member Author

ttuegel commented Feb 2, 2016

@edolstra Well, the wrapper script was missing bzip2, so if you weren't using the systemd service, it was already broken. But @dezgeg pointed out (rightly) that all systemd services are having their PATH set improperly; we should be doing map (pkg: pkg.bin or pkg) pkgs for the packages listed there.

@edolstra
Copy link
Member

edolstra commented Feb 2, 2016

That seems hacky. Why pkg.bin or pkg? Why not pkg.bin or pkg.bin or ... or pkg? Rather, it should use whatever outputs would be installed into a user environment by default.

@ttuegel
Copy link
Member Author

ttuegel commented Feb 2, 2016

Rather, it should use whatever outputs would be installed into a user environment by default.

Yes, absolutely. That's what I meant. I may not have quoted the expression correctly. 😃

@dezgeg
Copy link
Contributor

dezgeg commented Feb 2, 2016

And for clarification: this is what the closure-size branch currently uses for choosing what to install in the user environment: pkg.bin or pkg.out or pkg.
#12653 for the discussion on that.

@ttuegel
Copy link
Member Author

ttuegel commented Feb 8, 2016

And for clarification: this is what the closure-size branch currently uses for choosing what to install in the user environment: pkg.bin or pkg.out or pkg.

No, because that PR was never merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

0.kind: bug Something is broken 6.topic: closure size The final size of a derivation, including its dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants