date:20170227

[Nix-commits] [NixOS/nixpkgs] 0d31a7: virtualbox: fix build

2017-02-27 Thread Alexey Shmalko

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 0d31a76813532a5a1a1d83b0f92c283206783f00
  
https://github.com/NixOS/nixpkgs/commit/0d31a76813532a5a1a1d83b0f92c283206783f00
  Author: Alexey Shmalko 
  Date:   2017-02-28 (Tue, 28 Feb 2017)

  Changed paths:
M pkgs/applications/virtualization/virtualbox/default.nix

  Log Message:
  ---
  virtualbox: fix build

The issue was caused by upgrading `qt` from `qt56` to `qt57`, which
now requires C++11.

For more info, see https://github.com/NixOS/nixpkgs/issues/23257.


___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

[Nix-commits] [NixOS/nixpkgs] 9431e4: ocamlPackages.ppx_tools: init at 5.0+4.05

2017-02-27 Thread Vincent Laporte

  Branch: refs/heads/master
  Home:   https://github.com/NixOS/nixpkgs
  Commit: 9431e49822eca4829c3075d993d77e10df88bf57
  
https://github.com/NixOS/nixpkgs/commit/9431e49822eca4829c3075d993d77e10df88bf57
  Author: Vincent Laporte 
  Date:   2017-02-28 (Tue, 28 Feb 2017)

  Changed paths:
M pkgs/development/ocaml-modules/ppx_tools/default.nix

  Log Message:
  ---
  ocamlPackages.ppx_tools: init at 5.0+4.05


  Commit: 52507b3a9b2f9055594886250994a73871061ca0
  
https://github.com/NixOS/nixpkgs/commit/52507b3a9b2f9055594886250994a73871061ca0
  Author: Vincent Laporte 
  Date:   2017-02-28 (Tue, 28 Feb 2017)

  Changed paths:
M pkgs/development/tools/ocaml/ocp-build/default.nix

  Log Message:
  ---
  ocamlPackages.ocp-build: 1.99.17-beta -> 1.99.18-beta


Compare: https://github.com/NixOS/nixpkgs/compare/1f779398c9a4...52507b3a9b2f___
nix-commits mailing list
nix-comm...@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-commits

Re: [Nix-dev] Best Practices on Modularizing Configuration.nix?

2017-02-27 Thread Profpatsch

On 17-02-27 09:15am, Mark Gardner wrote:
> Now that I am putting NixOS on more and more machines, I would like to
> modularize and share parts of the config to maximize reuse and ensure
> uniformity.

As far as the non-dev-ops-y parts go
(that is: the nix expression parts),
there’s basically two ways to structure modules:

1. Using `import`
2. Using `imports` from the module system
3. Using option definitions

All have their place, I personally use the first
two for more ephemeral settings and the latter if
I want to share something for use by others.

Example from my current machine config in our vuizvui repo:

I have a folder for my personal machines, with a lib.nix
and pkgs.nix; these are included as attrsets with `import`
https://github.com/openlab-aux/vuizvui/blob/ac8da8796649e463b7d31dad6bfc95f01008c787/machines/profpatsch/katara.nix#L4

My config for workstation/server/base is split into various
module files, which get included with `imports`.
https://github.com/openlab-aux/vuizvui/blob/ac8da8796649e463b7d31dad6bfc95f01008c787/machines/profpatsch/katara.nix#L9
https://github.com/openlab-aux/vuizvui/blob/ac8da8796649e463b7d31dad6bfc95f01008c787/machines/profpatsch/base-workstation.nix#L11

Then finally there’s the Thinkpad-specific setup,
which I have put into a module with an enable option
for others to use.
https://github.com/openlab-aux/vuizvui/blob/ac8da8796649e463b7d31dad6bfc95f01008c787/machines/profpatsch/katara.nix#L45
https://github.com/openlab-aux/vuizvui/blob/ac8da8796649e463b7d31dad6bfc95f01008c787/modules/hardware/thinkpad.nix
and it’s actually used by our hackerspace’s Thinkpad, too:
https://github.com/openlab-aux/vuizvui/blob/cd4bc6fde00e3da0382a3eb151dbbd0087449377/machines/labnet/labtops.nix#L9

I hope that helps.

--
Proudly written in Mutt with Vim on NixOS.
Q: Why is this email longer than five sentences?
A: Sometimes you have to be more verbose. :)
May take up to five days to read your message. If it’s urgent, call me.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

81 matches

Mail list logo