The previously used PR specific urls do cease to exist after a force
push to the PR branch.
Also manually enable hydra builds for reflex-dom-core until upstream
provides a better fix.
https://github.com/kovidgoyal/kitty/releases/tag/v0.18.0
I submitted a patch to kitty, so that the library paths can now be passed as arguments to the build system, eliminating the need for patching. This should reduce the required maintenance effort in the future.
This commit removes the dependency on `which`, which is no longer necessary since 5e4fe584fa. It was introduced in 481e61fad8.
The configure phase is now ignored because kitty has no configure script.
The kitty tests are now run after compilation.
The zsh completions no longer need to be invoked with `source` since 38eb737845, so remove the outdated comment.
There is now a link to the changelog.
This should no longer be needed with python3 because it's now
set correctly in the interpreter.
Note that the build currently fails with and without this change.
This can be used to explicitly specify a specific dtb file, relative to
the dtb base.
Update the generic-extlinux-compatible module to make use of this option.
Some bootloaders might not properly detect the model.
If the specific model is known by configuration, provide a way to
explicitly point to a specific dtb in the extlinux.conf.
This option exposes the builder command used to populate an image,
honoring all options except the -c <path-to-default-configuration>
argument.
Useful to have for sdImage.populateRootCommands.
Special care needs to be taken w.r.t cross - the populate command runs
on the host platform, the activation script on the build platform (so
the builders differ)
Keeping the VM state test across several run sometimes lead to subtle
and hard to spot errors in practice. We delete the VM state which
contains (among other things) the qcow volume.
We also introduce a -K (--keep-vm-state) flag making VM state to
persist after the test run. This flag makes test-driver.py to match
its previous behaviour.
Turns out, on smaller images (~800MiB uncompressed sdcard image size),
the current fudge factor is way too small to even get the system to the
phase where it can resize itself.
I first tried with 1.05, but it wasn't enough.
Malte Brandy