frog: init at v0.13.7

[roberth]

Motivation for this change

frog is a natural language parser for dutch.
It depends on some other packages in the LanguageMachines organisation.
I have included an update script.

Things done

Please check what applies. Note that these are not hard requirements but merely serve as information for reviewers.

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

---

[Mic92]

As it is not part of the main namespace, the packages will be not build by hydra. Are you ok with this?

[roberth]

That's a very good point! I will make frog available at the top level. I don't think its dependencies are used a lot outside frog, so I think it doesn't make sense to put everything in the already big all-packages.nix.

Is there a way to also include my test without polluting all-packages.nix? (It's a simple runCommand derivation that makes sure frog works as expected without a mutable frog.out, lingering builder state, etc.)

[Mic92]

You can add it to checkPhase, so it will be run when the package is build.

[FRidh]

As it is not part of the main namespace, the packages will be not build by hydra

Its possible to use recurseIntoAttrs

[roberth]

• Added recurseIntoAttrs to also build test and any other languagemachines projects that may be added in the future
• Rebased onto master

Thanks @Mic92 and @FRidh for the review and help!

Ready for merge, as far as I'm concerned.

[Mic92]

Your test seems to be not working:

$ nix-shell --keep-going -p languageMachines.test
bash: /nix/store/6jaydhdipi87z9i4p8czq46nj2ga04ni-frog-test: line 1: syntax error near unexpected token `('

[roberth]

I would expect Travis CI to catch that. I will look into it.

[roberth]

Alright, what happens is that nix-shell wants to run the output of the test. I have no idea why that happens, because for example

nix-shell --keep-going -p languageMachines.frog

does not run the executable. I did't expect nix-shell -p to try to run text files as scripts. (Did you?)

The following works and seems sufficient:

nix-build -A languageMachines.test '<nixpkgs>'

I think the nix-shell behaviour might be a bug.

[Mic92]

I guess it is ok then.