4c16325de0
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 |
||
---|---|---|
.. | ||
arch | ||
bazaar | ||
codeville | ||
cvs | ||
cvs2svn | ||
cvsps | ||
darcs | ||
fossil | ||
git-and-tools | ||
guitone | ||
kdesvn | ||
meld | ||
mercurial | ||
monotone | ||
monotone-viz | ||
rapidsvn | ||
rcs | ||
subversion | ||
tailor | ||
tkcvs | ||
veracity | ||
viewmtn |