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

unigine-valley: init at 1.0-1 #19813

Closed
wants to merge 1 commit into from
Closed

Conversation

kierdavis
Copy link
Contributor

Motivation for this change

Add Unigine Valley GPU benchmarking application. Provides one executable, valley, which starts the launcher (from which you can configure graphics settings before beginning the benchmark).

Things done
  • Tested using sandboxing
    (nix.useSandbox on NixOS,
    or option build-use-sandbox 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.

Sandboxing tested by setting nix.useSandbox = true and running nix-shell -I nixpkgs=. -p unigine-valley --run valley in a local checkout of this branch.

@mention-bot
Copy link

@kierdavis, thanks for your PR! By analyzing the history of the files in this pull request, we identified @zimbatm, @edolstra and @peti to be potential reviewers.

@kierdavis kierdavis changed the title unigine-valley: init at 1.0 unigine-valley: init at 1.0-1 Oct 23, 2016
description = "The Unigine Valley GPU benchmarking tool";
homepage = "http://unigine.com/products/benchmarks/valley/";
license = stdenv.lib.licenses.unfree; # see also: /nix/store/*-unigine-valley-1.0/opt/unigine/valley/documentation/License.pdf
maintainers = [ stdenv.lib.maintainers.kier ]; # Kier Davis <kierdavis@gmail.com>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this information can be looked up in the maintainers file, I would not put the comment here

@grahamc
Copy link
Member

grahamc commented Oct 24, 2016

I've just merged this in to master. Thank you for your contribution. I've made two changes:

  1. Renamed your maintainer entry form kier to kierdavis to match your github user
  2. Removed the comment about your email address from the package

Thank you!

@kierdavis
Copy link
Contributor Author

Awesome, thanks!

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

Successfully merging this pull request may close these issues.

None yet

5 participants