On 07/07/17 10:28, Harmen via nix-dev wrote:
On Fri, Jul 07, 2017 at 07:59:46AM +0200, Vladimír Čunát wrote:
On 07/06/2017 07:35 PM, Harmen via nix-dev wrote:
Does that makes sense? Did I forget a 'name' somewhere?
When you use things like
src = ./.;
the directory gets copied into nix
On Fri, Jul 07, 2017 at 07:59:46AM +0200, Vladimír Čunát wrote:
> On 07/06/2017 07:35 PM, Harmen via nix-dev wrote:
> > Does that makes sense? Did I forget a 'name' somewhere?
>
> When you use things like
> src = ./.;
> the directory gets copied into nix store and the resulting path's name
> is
On 07/06/2017 07:35 PM, Harmen via nix-dev wrote:
> Does that makes sense? Did I forget a 'name' somewhere?
When you use things like
src = ./.;
the directory gets copied into nix store and the resulting path's name
is based on the name of the directory.
--Vladimir
On Thu, Jul 06, 2017 at 06:35:15PM +0200, Harmen via nix-dev wrote:
> Hello all,
> another day, another problem :/
>
> I'm trying to figure out why a build generates different build IDs in
> different
> contexts.
> I have a nix expression and some code. If I copy that from machine A
> to machine
Hello all,
another day, another problem :/
I'm trying to figure out why a build generates different build IDs in different
contexts.
I have a nix expression and some code. If I copy that from machine A
to machine B they both give the same build hash. All's fine there.
If on machine B I run
