Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- ran `/nix/store/fnypnfihpivkzgwrpi3g6r7ag5psfdim-verilator-3.922/bin/verilator_bin -V` and found version 3.922
- ran `/nix/store/fnypnfihpivkzgwrpi3g6r7ag5psfdim-verilator-3.922/bin/verilator_bin --version` and found version 3.922
- ran `/nix/store/fnypnfihpivkzgwrpi3g6r7ag5psfdim-verilator-3.922/bin/verilator_bin_dbg -V` and found version 3.922
- ran `/nix/store/fnypnfihpivkzgwrpi3g6r7ag5psfdim-verilator-3.922/bin/verilator_bin_dbg --version` and found version 3.922
- ran `/nix/store/fnypnfihpivkzgwrpi3g6r7ag5psfdim-verilator-3.922/bin/verilator_coverage_bin_dbg -V` and found version 3.922
- ran `/nix/store/fnypnfihpivkzgwrpi3g6r7ag5psfdim-verilator-3.922/bin/verilator_coverage_bin_dbg --version` and found version 3.922
- ran `/nix/store/fnypnfihpivkzgwrpi3g6r7ag5psfdim-verilator-3.922/bin/verilator -V` and found version 3.922
- ran `/nix/store/fnypnfihpivkzgwrpi3g6r7ag5psfdim-verilator-3.922/bin/verilator --version` and found version 3.922
- ran `/nix/store/fnypnfihpivkzgwrpi3g6r7ag5psfdim-verilator-3.922/bin/verilator_coverage -V` and found version 3.922
- ran `/nix/store/fnypnfihpivkzgwrpi3g6r7ag5psfdim-verilator-3.922/bin/verilator_coverage --version` and found version 3.922
- ran `/nix/store/fnypnfihpivkzgwrpi3g6r7ag5psfdim-verilator-3.922/bin/verilator_profcfunc help` got 0 exit code
- found 3.922 with grep in /nix/store/fnypnfihpivkzgwrpi3g6r7ag5psfdim-verilator-3.922
- directory tree listing: https://gist.github.com/04b5044a54bb4ff549696cbcd57cd88e
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 4.0.0 with grep in /nix/store/k8xscjzkd9w5n6hly18qcwgg62m3fjh9-krita-4.0.0
- directory tree listing: https://gist.github.com/c2d48bc58cc453eac241620389f2b9ce
Also change to use jbuilder for build per upstream instructions. In this case, the build needs to be
driven by jbuilder but opam still needs to be in PATH.
`zed` is obviously dead and not maintained anymore
(https://zef.me/how-to-abandon-open-source-d5ebbc6e45e5).
As the last upstream commit was in 2015 we faced and will face many
issues with its dependencies due to the outdated upstream which can be
fatal when having security issues in the NodeJS ecosystem to fix.
One example is the handling of `nwjs` which is currently version `0.23`,
but `zed` relies on `0.9`. In order to reduce the maintenance overload
because of dead packages it's better to get rid of `zed` entirely.
Fixes#37361
