nixpkgs

philipp/nixpkgs

Fork 0

Commit graph

Author	SHA1	Message	Date
aszlig	623f1940c0	vm/windows: Make list of dependencies explicit. So far, the VMs have always been using the native architecture, because it was reimporting <nixpkgs> several times. Now, we propagate a list of packages down to all sub-imports, which not only makes clearer which dependencies a part actually has, but also will make it easier in case we want to refactor those parts to use callPackage. Signed-off-by: aszlig <aszlig@redmoonstudios.org>	2014-02-26 05:43:34 +01:00
aszlig	d8e66722a3	vm/windows: Factor out bootstrapping process. This now isolates the vmTools integration from the bootstrap process and thus removes our fixed Windows ISO and product key. The latter can now be provided by an attribute "windowsImage" to runInWindowsVM. Signed-off-by: aszlig <aszlig@redmoonstudios.org>	2014-02-26 04:52:01 +01:00

Author

SHA1

Message

Date

aszlig

623f1940c0

vm/windows: Make list of dependencies explicit.

So far, the VMs have always been using the native architecture, because
it was reimporting <nixpkgs> several times. Now, we propagate a list of
packages down to all sub-imports, which not only makes clearer which
dependencies a part actually has, but also will make it easier in case
we want to refactor those parts to use callPackage.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>

2014-02-26 05:43:34 +01:00

aszlig

d8e66722a3

vm/windows: Factor out bootstrapping process.

This now isolates the vmTools integration from the bootstrap process and
thus removes our fixed Windows ISO and product key. The latter can now
be provided by an attribute "windowsImage" to runInWindowsVM.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>

2014-02-26 04:52:01 +01:00

2 commits