For dirty dirty hacks, you can set __noChroot = true and get access to the
network.
Okay, now I know how to implement it. I'll try to keep it clean.
Thanks
--
Georges
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
I don't like to use the git hash, as it is SHA1 and not fit for use wrt
integrity. I think that would be a regression wrt the complex tricks that
Georges referred to.
Would it be possible to create a git wrapper that does the
make_deterministic_repo step in a transparent manner for cargo and
For dirty dirty hacks, you can set __noChroot = true and get access to the
network.
On Jan 2, 2015, at 1:09 PM, Georges Dubus georges.du...@gmail.com wrote:
Hello everyone
I would like to propose compromise in the purity rules of non-fixed-output
derivations, and hear what you think
Hello everyone
I would like to propose compromise in the purity rules of non-fixed-output
derivations, and hear what you think about it.
# Rationale
There are a few situations where derivations play the role of fixed-output
derivation, but the hash of their output is not fixed. Some examples:
-
I've talked to git (irc) long time ago, they are pretty sure that the git
hash would serve well as alternative to a sha256 or md5 hash.
Thus adding an implementation for
mkDerivation {
git_hash = ; # instead of fixed output hash
}
and have the nix implementation check for $out/.git and, git
Another use-case: providing the same input hash, based only on version, for
gcc and cross-gcc on another platform. Ditto for ccache and distcc.
On Fri, Jan 2, 2015, 14:56 Shea Levy s...@shealevy.com wrote:
For dirty dirty hacks, you can set __noChroot = true and get access to the
network.
On
