jp: init at 0.1.2

[cransom]

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

• Tested using sandboxing
  (nix.useChroot on NixOS,
  or option build-use-chroot in nix.conf
  on non-NixOS)
• Built on platform(s)
  • NixOS
  • OS X
  • Linux
• 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/)
• Fits CONTRIBUTING.md.

---

A json parson tool based on the JMESPATH query language.
http://jmespath.org/

[matthewbauer]

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.

[cransom]

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.

[kamilchm]

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.

[cransom]

Ahhh. I got it. I've pulled the override. #16129 (comment) explained it for me.