jp: init at 0.1.2 #17131
jp: init at 0.1.2 #17131
Conversation
| @@ -2141,6 +2143,8 @@ in | |||
| gcc = gcc49; # doesn't build with gcc5 | |||
| }; | |||
|
|
|||
| jp = (callPackage ../development/tools/jp { }).bin // { outputs = [ "bin" ]; }; | |||
There was a problem hiding this comment.
I see some other derivations doing this but it seems a little backwards to me... Shouldn't "outputs" be in jp/default.nix and not here? I guess it's fine but I don't see why you would override outputs.
There was a problem hiding this comment.
I didn't quite follow at first either, but I looked at a few of the other Go apps and copied the behavior. Crawling through nixpkgs looking at how Go packages were created, I found https://nixos.org/releases/nixpkgs/nixpkgs-16.09pre86545.65ac26e/manual/#ex-buildGoPackage which mentions how it generates multiple outputs. Running a nix-build . -A jp.all or jp.bin got what I wanted but thats not the normal experience I expect with installing packages.
Maybe it could be spelled out more thoroughly in the docs? There's just a bit more going on behind the scenes with buildGoPackage. For this one, I'm only interested in the bin/ directory and want to discard the rest of the output as there's nothing useful in there.
Also, fwiw, this is building on my mac but it did take a good long time for the compilation to finish, travis appears to be building a lot and it didn't finish.
There was a problem hiding this comment.
We had a discussion about it here #16129 (comment)
Running a nix-build . -A jp.all or jp.bin got what I wanted but thats not the normal experience > I expect with installing packages.
You don' normally install packages by nix-build - it's meant to be used as development tool.
If you install a package with nix-env -i you don't need to specify package output.
A json parson tool based on the JMESPATH query language. http://jmespath.org/
|
Ahhh. I got it. I've pulled the override. #16129 (comment) explained it for me. |
Motivation for this change
It's not that we really need more JSON parsers in the world, but AWS happened to choose an implementation and embedded it in their CLI tools. This is a standalone utility into that library.
Things done
(nix.useChroot on NixOS,
or option
build-use-chrootinnix.confon non-NixOS)
nix-shell -p nox --run "nox-review wip"./result/bin/)A json parson tool based on the JMESPATH query language.
http://jmespath.org/