Nicolas B. Pierron

@zeorin I recall we had a live discussion about this topic on Matrix. Last time we spoke about changing the way the Firefox wrapper is handled in Nixpkgs, as this...

4 things are downloaded: - the gpg key (checked using hard coded checksum) - the `firefox_versions.json` file. (https only) - the checksum file. [beta / release] (verified using the gpg...

Currently the `policies.json` is inherited from https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/networking/browsers/firefox-bin/default.nix#L179 It is used as follow: https://github.com/mozilla/nixpkgs-mozilla/blob/master/firefox-overlay.nix#L142-L154 Which reuses the building expression from Nixpkgs, and replaces the source binary. While this can be done...

When using rust-analysis, you should explicit it as part of the extensions to be included: ``` ((nixpkgs.rustChannelOf { date = "2021-08-15"; channel = "nightly"; }).rust.override (old: { extensions = ["rust-src"...

This is not the goal of this repository to pin a specific nightly. If we were pinning any version, then the nightly version would no longer be the `latest`, as...

@dysinger I have not noticed any issue when using the rust-overlay natively on arm64 devices. Here is the location where the mapping between the system and the tarball to be...

I am open to both, the problem I see with this approach is that `mach` might try to be clever based on programs which are installed, such as downloading the...

I have been told that wayland support can be enabled by setting the environment variable `MOZ_ENABLE_WAYLAND` which will default to either x11 or wayland based on the commit message which...

hum … it sounds that when we are building with clang, we should use clang as much as possible for the `libclang-path` and the `clang-path`.

Fixing the first issue lead to another issue which made me to not investigate more in the first place, which is: ``` 0:18.27 make[4]: *** […/src/config/rules.mk:801: Unified_cpp_xpcom_threads0.o] Error 1 0:18.27...