| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
| |
I think this is more descriptive, and "img" is a name better used for
VM images.
Signed-off-by: Alyssa Ross <hi@alyssa.is>
Message-Id: <20221009114036.463071-6-hi@alyssa.is>
|
| |
|
|
|
|
|
|
|
|
| |
Previously there were hardcoded "x64" in EFI loaders' filenames.
Signed-off-by: Ivan Nikolaenko <ivan.nikolaenko@unikie.com>
Message-Id: <20220929103234.2460828-1-ivan.nikolaenko@unikie.com>
Reviewed-by: Alyssa Ross <alyssa.ross@unikie.com>
Tested-by: Alyssa Ross <alyssa.ross@unikie.com>
Signed-off-by: Alyssa Ross <alyssa.ross@unikie.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
When cross compiling Spectrum OS for aarch64 it tries to run aarch64
binaries on x64 host. To fix this issue it is possible to add
pkgsBuildHost prefix to all native build inputs. However, a better
option would probably be to use callPackage function. With that change
it is able to automatically select correct packages.
Signed-off-by: Yuri Nesterov <yuriy.nesterov@unikie.com>
Message-Id: <20220927123318.2531867-1-yuriy.nesterov@unikie.com>
Signed-off-by: Alyssa Ross <alyssa.ross@unikie.com>
|
| |
|
|
|
|
|
|
|
|
| |
This allows to get access to rootfs and kernel from device images.
Signed-off-by: Yuri Nesterov <yuriy.nesterov@unikie.com>
Message-Id: <20220922144719.816016-1-yuriy.nesterov@unikie.com>
Tested-by: Ville Ilvonen <ville.ilvonen@unikie.com>
Reviewed-by: Alyssa Ross <alyssa.ross@unikie.com>
Signed-off-by: Alyssa Ross <alyssa.ross@unikie.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
By default, a file called "config.nix" in the root of the Spectrum
repository will be read if it exists. That file should contain an
attribute set. Currently, only a "pkgs" key is supported, which
allows specifying a custom package set that will be used throughout
the Spectrum Nix files. This will allow us to provide configuartion
options for people who want to build Spectrum in ways that are
probably not suitable for upstreaming.
For example, using the "pkgs" config option I'm introducing here, it
would be possible to use an overlay to patch individual components,
like so:
{
pkgs = import <nixpkgs> {
overlays = [
(final: super: {
weston = super.weston.overrideAttrs ({ patches ? [], ... }: {
patches = patches ++ [
path/to/weston.patch
];
});
})
];
};
}
Signed-off-by: Alyssa Ross <hi@alyssa.is>
Message-Id: <20220831093727.282797-1-hi@alyssa.is>
Reviewed-by: Ville Ilvonen <ville.ilvonen@unikie.com>
Tested-by: José Pekkarinen <jose.pekkarinen@unikie.com>
|
| |
|
|
|
|
|
| |
This will save having to download gcc and binutils just to change a
config file in a VM.
Signed-off-by: Alyssa Ross <hi@alyssa.is>
|
| |
|
|
|
|
| |
Nix files shouldn't be considered part of the sources, and so they
should be filtered out. This way, changes to them (that don't change
their meaning) won't force rebuilds.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will make it easier to dual-boot Spectrum with other operating
systems, and hopefully make it possible to avoid chainloading (which
has firmware compatibility issues) in the combined image.
We're not exactly following Boot Loader Specification[1] best
practices here — we don't namespace installation by version or
machine-id. But it's better than what we had before, and I think
it'll be easier to figure out what to do about namespacing once we've
figured out how updates will work.
[1]: https://systemd.io/BOOT_LOADER_SPECIFICATION/
Cc: Puck Meerburg <puck@puckipedia.com>
Message-Id: <20220420101214.1228221-2-hi@alyssa.is>
|
|
|
This way, we don't need to a build a whole huge image to test changes
to the installer system. In fact, we don't need to build an image for
it at all — we can just run it in a VM with root on 9p.
|