ahhh I never used it. I will! Thank you.
On Sun, Sep 28, 2014 at 08:11:30PM -0400, Shea Levy wrote:
Yes, this is exactly what replaceDependency is for.
On Sun, Sep 28, 2014 at 02:58:03PM -0700, rocon...@theorem.ca wrote:
We already have shlevy's replaceDependency which, IMHO, solves this
Hello!
It could be nice if we had a nix derivation attribute that allowed the
determination of a store path, overriding the hash mechanisms for it.
Imagine that we have a bash to fix; we could add a line in the bash derivation
attribute set:
forceOut = whatever store path out
It'd be nice
My 'forceOut' clearly will not work as easy as setting it in a
stdenv.mkDerivation argument, because there may be multiple calls to
mkDerivation for the same derivation name (with different inputs).
The table of correspondences in nix.conf still looks good to me though.
It'd be nice if there
We already have shlevy's replaceDependency which, IMHO, solves this
problem.
In functional programming when we have an immutable tree structure that we
want to update, we trace a path from the root of the tree to the node that
we want to update and we update all the nodes along that path to
Yes, this is exactly what replaceDependency is for.
On Sun, Sep 28, 2014 at 02:58:03PM -0700, rocon...@theorem.ca wrote:
We already have shlevy's replaceDependency which, IMHO, solves this
problem.
In functional programming when we have an immutable tree structure that we
want to update, we
