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

Jump to bottom

clprover: init at 1.0.3 #56403

Merged
merged 3 commits into from Feb 26, 2019
Merged

clprover: init at 1.0.3 #56403

merged 3 commits into from Feb 26, 2019

Conversation

mgttlinger
Copy link
Member

Motivation for this change

There was no derivation for clprover.

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.

@7c6f434c
Copy link
Member

@GrahamcOfBorg build clprover

@7c6f434c
Copy link
Member

Could you please set meta.platforms? Apparently upstream doesn't care outside of x86_64-linux, which is OK but probably worth recording.

@7c6f434c 7c6f434c merged commit 5781856 into NixOS:master Feb 26, 2019
@7c6f434c
Copy link
Member

Thanks

@mgttlinger mgttlinger deleted the clprover branch February 26, 2019 12:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
8.has: package (new) 10.rebuild-darwin: 0 10.rebuild-linux: 1-10 11.by: package-maintainer
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@mgttlinger @7c6f434c @GrahamcOfBorg