This also means adding a lowPrio wrapper, because without it nix-env
would prefer the "-full" expression over the normal one.
Maybe that's desirable, even?
svn path=/nixpkgs/trunk/; revision=26828
Several changes, some highlights:
* Structure of haskell-packages.nix updated. It's now easier to
select different default versions of packages for different
versions of GHC.
* GHC 7.0.2 is now default.
* Haskell Platform 2011.2.0.0 has been added and is now default.
* Several packages have been updated
(gtk2hs, gitit, xmonad, darcs, ...).
* Some old packages have been removed.
svn path=/nixpkgs/trunk/; revision=26288
Patch Tcl/Tk scripts to invoke 'wish' using the complete executable path to
ensure that the proper version is being used.
svn path=/nixpkgs/trunk/; revision=25755
`perl.name' evaluates to "perl" (since there are not enough
characters in the string). It's better to use
builtins.parseDrvName.
svn path=/nixpkgs/trunk/; revision=25559
The postInstall hook replaces identical copies of the same files in $out with
symlinks. This patch changes the call to 'ln' to pass the '-v' flag so that we
can see in the build log which files were replaced.
svn path=/nixpkgs/trunk/; revision=25455
The "find -print | while read" loop failed to deal with paths that contain
whitespace. Instead, we now use a similar construct that's based on globbing.
svn path=/nixpkgs/trunk/; revision=25454
The git-gui module cannot be wrapped like gitk, because the Tcl implementation
uses the program's basename to determine stuff like the name of the Window it
opens, etc., and it cannot deal with a program name that contain a dot, like
".git-gui-wrapped" did.
Instead of wrapping git-gui, it's now patched to execute 'wish' with a complete
store path.
While I was at it, I also applied this solution to git-gui--askpass.
svn path=/nixpkgs/trunk/; revision=25453
I take action before much discussion.
For what I see:
- getPkgConfig problems are hard to track
- config.nix trying to forecast getPkgConfig behaviour looks me as a bad approach,
and people should not trust such a config.nix unless they parsed the whole nixpkgs
for tricky effects.
- It's not that hard to write config.nix in the style of getConfig
- Every now and then newcomers hit the "'git' is an attribute set while a boolean was expected".
Maybe this will disrupt nixes of some people, and that will be a background on what to discuss.
svn path=/nixpkgs/trunk/; revision=25314
