| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Conflicts:
pkgs/applications/graphics/hello-wayland/default.nix
pkgs/applications/virtualization/cloud-hypervisor/default.nix
pkgs/applications/window-managers/tinywl/default.nix
pkgs/applications/window-managers/wayfire/applications.nix
pkgs/applications/window-managers/wayfire/default.nix
pkgs/applications/window-managers/wayfire/wcm.nix
pkgs/applications/window-managers/wayfire/wf-config.nix
pkgs/applications/window-managers/wayfire/wf-shell.nix
pkgs/development/libraries/wlroots/default.nix
pkgs/os-specific/linux/chromium-os/crosvm/default.nix
pkgs/os-specific/linux/kernel/common-config.nix
pkgs/os-specific/linux/kernel/patches.nix
pkgs/os-specific/linux/mdevd/default.nix
pkgs/os-specific/linux/s6-linux-init/default.nix
pkgs/top-level/all-packages.nix
|
| |
|
|
|
|
|
|
|
|
|
| |
* Add new vhost source dependency
* Drop Cargo.lock patch
* Re-enable test on x86_64 (seems to work fine now)
* Drop syslog patch
* Rebase VIRTIO_NET_F_MAC patch -- I renamed TapFdOptions to
TapFdOption for consistency with newly-added similar structs.
Message-Id: <20210603091138.24942-4-hi@alyssa.is>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* chromiumOSPackages.linux: fix config
* chromiumOSPackages.common-mk: update patches
* chromiumOSPackages.vm_protos: drop GN patch
The missing dependency has been added upstream.
* chromiumOSPackages.common-mk: disable clang-only warnings
* chromiumOSPackages.sommelier: update patches
Support for stable xdg-shell was implemented in upstream Sommelier,
but then reverted because the GTK version that comes with the Debian
in the container Chromium OS uses was too old to support it.
That's not a problem for us, of course, but it does mean that we can
use an upstream implementation of xdg-shell. So here I switch from
using Puck's implementation, to reverting the revert of the upstream
one.
* crosvm: fix outdated Cargo.lock from upstream
* crosvm: update VIRTIO_NET_F_MAC patch (renamed to be less annoying)
* crosvm: add new dependencies
* crosvm: patch boot test so it doesn't fail because of no /dev/log.
* crosvm: disable boot test on x86_64 because it often hangs on the AMD
EPYC 7401P 24-Core Processor I was testing it on (but not my Intel(R)
Core(TM) i5-2520M CPU @ 2.50GHz).
* spectrumPackages.linux: drop evged patch
This has reached the Chromium OS kernel now, so we don't need to apply
it ourselves any more.
Co-authored-by: Alyssa Ross <hi@alyssa.is>
Cc: Puck Meerburg <puck@puckipedia.com>
Reviewed-by: Alyssa Ross <hi@alyssa.is>
Tested-by: Alyssa Ross <hi@alyssa.is>
Message-Id: <20210529144117.571353-2-hi@alyssa.is>
Message-Id: <20210529144117.571353-3-hi@alyssa.is>
Message-Id: <20210529144117.571353-4-hi@alyssa.is>
Message-Id: <20210529144117.571353-5-hi@alyssa.is>
Message-Id: <20210529144117.571353-6-hi@alyssa.is>
Message-Id: <20210529144117.571353-7-hi@alyssa.is>
Message-Id: <20210529144117.571353-8-hi@alyssa.is>
Message-Id: <20210529144117.571353-9-hi@alyssa.is>
|
| |
|
|
|
|
|
| |
This will be important for host-based networking in Spectrum.
Message-Id: <20210411115740.29615-7-hi@alyssa.is>
Reviewed-by: Cole Helbling <cole.e.helbling@outlook.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
crosvm now needs the Minijail sources. However, it'll notice that a
Minijail package is provided via pkg-config, and then not actually use
those sources or build its own Minijail. It would be nice if the
Minijail we provide could be the same version as in Chromium OS, which
means bringing Minijail under chromiumOSPackages.
A couple of backports are no longer required; one to common-mk and one
to Linux. A new patch to fix a parallel build failure has been
introduced.
Message-Id: <20200602005619.31128-1-hi@alyssa.is>
Thanks-to: Michael Raskin <7c6f434c@mail.ru>
Reviewed-by: Cole Helbling <cole.e.helbling@outlook.com>
Tested-by: Cole Helbling <cole.e.helbling@outlook.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These changes make chromiumOSPackages.updateScript better understand
the Repo manifest format[1].
It now properly distinguishes between paths in the Chromium OS source
tree and paths on the git servers, which are usually not the same.
For example, chromiumos-overlay is located in the source tree at
src/third_party/chromiumos-overlay, but on chromium.googlesource.com
it's located at chromiumos/overlays/chromiumos-overlays. Components
are now keyed by their location in the Chromium OS source tree (and
packages have all been updated for this change.)
Additionally, it now understands Repo remotes. This means that it is
now possible to use a Chromium OS component like Minijail, which is
hosted on android.googlesource.com rather than
chromiumos.googlesource.com. This was not previously possible.
[1]: https://gerrit.googlesource.com/git-repo/+/HEAD/docs/manifest-format.md
Message-Id: <20200530190028.6388-1-hi@alyssa.is>
Reviewed-by: Cole Helbling <cole.e.helbling@outlook.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
I forgot to do this in a8b8108ec74c3fbc395ce7c497e6cbd55fac7172.
|
| | |
|
|
|
sommelier has a lot of dependencies on other Chromium OS packages. To
manage this mess, I introduced chromiumOSPackages to hold them all,
since most of them won't be useful aside from building other
Chromium OS packages, and chromiumOSPackages.common-mk, which is a
wrapper around stdenv to handle interacting with Chromium OS's
idiosyncratic GN-based build system.
I adapted crosvm's updateScript to become the updateScript for all of
chromiumOSPackages, and pulled crosvm under chromiumOSPackages. This
means that all Chromium OS packages use approximately the same
versions that are distributed as an upstream release.
There are still a couple of Chromium OS packages in Nixpkgs that
aren't part of this set. Pulling those in is future work.
|