| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Suggestion by @Profpatsch to introduce consistent behaviour of the top-
level expression so we can now use:
nix-build '<vuizvui>' -A machines.aszlig.tishtushi.build
.. the same way as:
nix-build '<vuizvui/machines>' -A aszlig.tishtushi.build
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The shortcut is mainly to make things a bit easier, instead of:
nix-build '<vuizvui/machines>' \
-A aszlig.tishtushi.eval.config.system.build.toplevel
We can now do something like this:
nix-build '<vuizvui/machines>' \
-A aszlig.tishtushi.build
... in order to get a system store path out of a machine definition.
This also fixes an evaluation error in the top-level default.nix. Thanks
to @Profpatsch for bringing this to my attention.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
| |
This file is just defaulting to <nixpkgs>, but we're going to substitue
it by the channel generator. We also need to make sure that we don't
have any other references to <nixpkgs>, but the latter can best be done
on Hydra's side if we don't make <nixpkgs> available to vuizvui builds.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
In the end we want to have something like (import <vuizvui> {}), which
exports all stuff we need for building machines, packages, providing
custom helper functions and much more. And all that by using a channel
instead of setting NIX_PATH directly :-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
