| 6 Mar 2025 |
 nbp | * Would merging the repositories help? | 10:42:24 |
| nbp | making one repository with both the content of both. | 10:42:40 |
 K900 | Both what? | 10:43:01 |
| K900 | flake-firefox-nightly and nixpkgs-mozilla? | 10:43:08 |
| nbp | I do not care. Apart from the historical value of nixpkgs-mozilla being the first overlay. | 10:43:34 |
| K900 | There's a bunch of other stuff in nixpkgs-mozilla | 10:43:51 |
| K900 | I'm not sure where that should go | 10:44:02 |
| nbp | yes, such as the toolchain I am using daily to compile Firefox / SpiderMonkey locally. | 10:44:12 |
| K900 | Maybe we can move in the direction of chopping it up into multiple repos | 10:44:31 |
| K900 | Given it's basically a bunch of mostly-independent bits that were dumped into a single repo for convenience and no real other reason | 10:45:14 |
| nbp | the Rust toolchain compiler, for staying up-to-date with the bleeding edge requirements from 2015, and the updates of the C++-layer translation which is also extremelly bleeding edge. | 10:45:18 |
| nbp | Well the convenience is being able to build Firefox from sources. | 10:45:48 |
| nbp | and contributing to it. | 10:46:03 |
| K900 | I mean the toolchain and firefox-bin being in the same repo | 10:46:09 |
| K900 | And I think there's a few other mostly unrelated overlays in there? | 10:47:01 |
| nbp | yes, to add an old version of gcc that is no longer capable of building firefox anymore. | 10:47:36 |
| K900 | Like there's a servo in there | 10:47:39 |
| K900 | And phlay | 10:47:42 |
| K900 | And git-cinnabar which we already have in nixpkgs and is also woefully outdated | 10:48:06 |
| nbp | phlay is an old tool for working with phabricator, to push changes. | 10:48:07 |
| K900 | And so on | 10:48:08 |
| K900 | Yeah but like, it doesn't need to be there, it should be in nixpkgs if people use it | 10:48:22 |
| nbp | well only people interested in Firefox contribution use these. | 10:48:47 |
| K900 | I think a lot of people use it for the Firefox overlay | 10:49:04 |
| nbp | My point is that nixpkgs-mozilla has lots of legacy, but they got introduced because of the needs to work on Firefox sources. | 10:51:02 |
| nbp | the binary were there only to provide a mean to stay up-to-date in a single command. | 10:51:53 |
 hexa | vcunat: https://github.com/NixOS/nixpkgs/pull/386854#issuecomment-2703585072 wdyt>? | 11:45:21 |
| hexa | * vcunat: https://github.com/NixOS/nixpkgs/pull/386854#issuecomment-2703585072 wdyt? | 11:45:23 |
 vcunat | It's a weird thing anyway, as FF 134+ should have ICU 76 (in the vendored libs), if I read this right:
https://bugzilla.mozilla.org/show_bug.cgi?id=1927706 | 11:58:17 |
| hexa | will probably take a look at how the icu packages of other distros look | 13:26:32 |
