Simplifies Firefox maintenance. See #160520
- make the firefox common.nix available from the top level as
buildMozillaMach
- use new buildMozillaMach function in librewolf expressions
- minor changes to update script
Feedreader is no longer activily maintained since 2019. The developer is working on a spiritual successor called NewsFlash.
https://web.archive.org/web/20220402032320/https://github.com/jangernert/FeedReader
Co-authored-by: pennae <82953136+pennae@users.noreply.github.com>
Co-authored-by: Rick van Schijndel <Mindavi@users.noreply.github.com>
This updates k3s.
This one's done by hand rather than via the update bot since the
upstream repo ended up in a state where `go mod download` didn't work,
and we had `proxyVendor` set (which causes a `go mod download`).
Deleting `proxyVendor` works now though, and I didn't actually fully
understand why it was needed before, so I've removed that. Which
unblocks the update.
The actual update was done via `./update.sh` after removing
`proxyVendor` and the `k3sServerVendorSha256` variables.
We can't just edit binary wrappers in place because of a length
mismatch, so we have to parse the generating makeCWrapper call out of
the binary, extract wrapper arguments from it and add them to the
Firefox wrapper.
All these contortions are needed because Firefox looks for its runtime
in argv0, so the proper argv0 needs to be set by wrappers to always
point to the "final" runtime. I think this could be avoided by wrapping
/lib/$libName/firefox instead of /bin/firefox, and I'd like to look into
that in the future, but for now I'm just fixing the immediate problem.
Without the change build on -fno-common toolchains like clamng-13 fails as:
$ nix build --impure --expr 'with import ./. {}; freetalk.override { stdenv = clang13Stdenv; }' -L
...
ld: more.o:src/./more.h:15: multiple definition of `cin'; primitives.o:src/./more.h:15: first defined here
ld: more.o:src/./more.h:14: multiple definition of `initial_settings'; primitives.o:src/./more.h:14: first defined here
This makes it easier to report bugs upstream and ensures that NixOS user crashes are fixed.
Based on my testing these reports weren't automatically submitted anyways so the privacy concern is minimal. For my crashes it both asked my if a crash report should be produced after a crash, and required manual sending. Although possibly the report world eventually be sent automatically.
Fixes https://github.com/NixOS/nixpkgs/issues/107889
Michael Weiss