[Nix-dev] Changes in cabal2nix version 20150525

2015-05-26 Thread Peter Simons
Hi folks,

I'd like to point out that cabal2nix version 20150525 -- which was added
in revision d808f5b3e669 -- brings three important changes you might want
to know about:

 1) Output generated by cabal2nix --shell now works for both nix-shell
and nix-build. In other words, you can execute

  $ nix-build shell.nix

to build your Haskell project with Nix. If that build fails with
strange compiler errors, then clear out the dist/ directory [1].

 2) The generated shell.nix expression accepts an argument called
compiler that chooses the GHC version to use for the build. For
example:

  $ nix-shell --argstr compiler ghc784
  $ nix-build shell.nix --argstr compiler ghc763

The default compiler is ghc7101. To see the list of available
compilers, run:

  $ nix-env -f nixpkgs -qaP -A haskell.compiler

  3) Files generated by cabal2nix no longer refer to haskellngPackages.
 That name is still valid, but it's obsolete now that Haskell NG has
 replaced the old infrastructure [2].

Best regards,
Peter



[1] https://github.com/NixOS/cabal2nix/issues/112
[2] 
https://github.com/NixOS/nixpkgs/blob/c0c82ea2ebbcf0632260a931cf832cac1c8a014e/pkgs/top-level/all-packages.nix#L14429-14430

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


Re: [Nix-dev] Using R with Bioconductor

2015-05-26 Thread Peter Simons
Hi Jeffrey,

  https://github.com/NixOS/nixpkgs/compare/master...jefdaj:bioc-pullreq

this looks good to me. Thank you very much for figuring this out!

The only thing I'd prefer is to have packages from CRAN and Bioconductor
in two separate files so that it's possible to re-generate them
separately. Both files should be imported into one attribute set called
rPackages, though, that's clear.

  There might be conflicts between the Bioconductor and CRAN release
  schedules.

I don't believe there's any release schedule. People just upload new
packages to the repository whenever they've finished a new version. I
doubt that's a coordinated effort.

Best regards,
Peter

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


[Nix-dev] Documenting nixpkgs.config options

2015-05-26 Thread Herwig Hochleitner
Contrary to nixos *module* options, which are self-documenting at
http://nixos.org/nixos/options.html, there is no equivalent documentation
for options available in nixpkgs.config. This is unfortunate, because a
recent blog post (http://blog.lastlog.de/posts/useflags_in_nixos/) makes
the very good point of framing them as a gentoo - useflag equivalent.

Thus users wanting to customize packages, are left with the option of
diving into the source, or hunting for wiki pages about their target
package, e.g. https://nixos.org/wiki/Enable_Browser_Plugins

https://github.com/NixOS/nixpkgs/issues/7446 is clearly relevant, however,
I'm primarily concerned with documentation right now, since I want users to
find the new wine options in the upcoming release.

Manually compiling a wiki page might work for now, but that will eventually
get outdated. Maintaining available flags in per-package metadata might be
better, but still risks running out of sync with careless commits.
Declaring a schema (a'la nixos-options), however, feels a little heavy
handed for nixpkgs.config.

Has there been work towards this? How should this be done?
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev


Re: [Nix-dev] Using R with Bioconductor

2015-05-26 Thread Jeffrey David Johnson
Sure that sounds good. It would make storing the mirror type for each
package unneccesary too. I'll see if I can set it up later today so
the script takes 'cran' or 'bioc' as an argument and reads/writes
cran-packages.nix or bioc-packages.nix, then default.nix can read both
sets and map the right urls onto them before combining.
Jeff

On Tue, 26 May 2015 10:35:21 +0200
Peter Simons sim...@cryp.to wrote:

 Hi Jeffrey,
 
   https://github.com/NixOS/nixpkgs/compare/master...jefdaj:bioc-pullreq
 
 this looks good to me. Thank you very much for figuring this out!
 
 The only thing I'd prefer is to have packages from CRAN and Bioconductor
 in two separate files so that it's possible to re-generate them
 separately. Both files should be imported into one attribute set called
 rPackages, though, that's clear.
 
   There might be conflicts between the Bioconductor and CRAN release
   schedules.
 
 I don't believe there's any release schedule. People just upload new
 packages to the repository whenever they've finished a new version. I
 doubt that's a coordinated effort.
 
 Best regards,
 Peter
 
 ___
 nix-dev mailing list
 nix-dev@lists.science.uu.nl
 http://lists.science.uu.nl/mailman/listinfo/nix-dev
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev