networkException

Moving that up before any build steps get run *does* work (see https://github.com/networkException/elk/commit/11e632662e59019dde849a5410a1778adb220436), which lead me to conclude that the variable gets set at build time (hence the feature request)...

winget should have all packages up to M127, see https://github.com/microsoft/winget-pkgs/commits/master/manifests/e/eloston/ungoogled-chromium

> emoji option in context menu is annoying Thats not an argument that would qualify for adding a removal patch. Not here (please take a look at the project goals)...

I avoided the nixpkgs issue largely because of its slightly convoluted history. Given that I both maintain ungoogled-chromium and it's nixpkgs packaging (CC @emilylange), I'll try to take a closer...

> Besides, this patch does not apply. that is a technical observation: ``` WARNING: Patch failed validation: extra/ungoogled-chromium/extension-search-path.patch DEBUG: Specifically, file "chrome/common/chrome_paths.cc" failed validation: Line '#include "base/files/file_path.h"' does not match...

*with my nixpkgs chromium maintainer hat on* I don't see the patch as useful here or in packaging as there are ways not needing modifications which I would prefer anyways

I think this has been discussed enough, solutions have been pointed out. This is definitely not a fit for us and very likely not for nixpkgs either. Closeing as per...

For the record, unless upstream provides a way to disable UI changes we are very unlikely to forward port anything given the high effort.

I don't understand

> Not putting in an effort to keep the classic UI available would mean forcing the new UI on Ungoogled Chromium users in the same way as Google is doing...