New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ungoogled-chromium: init at 81.0.4044.92-2 #76082
Conversation
, patch | ||
}: | ||
{ rev, sha256 }: | ||
stdenv.mkDerivation { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This expression lacks good whitespace like other expressions in nixpkgs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated whitespace.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you would like to package ungoogled-chromium, I think it should be its own package, with the upstream versions decoupled from chromium's versions. Chromium is already frequently difficult and time-consuming (as in, whole day down the drain) to update. I cannot hold back a new release with 50 CVE fixes just because the ungoogled-chromium patchset has not been updated yet. This would also burden the chromium maintainer with another 3+ hour build and smoke test.
ungoogled-chromium is basically a separate browser product, even if it is distributed as a patchset, so I recommend copying nixpkgs chromium/ into a new directory and replacing the maintainers :-)
I'd be willing to copy/paste into a new package. I agree that the chromium release should not be held back due to a delay in the patchset release. |
78822b4
to
ef5e9ce
Compare
I updated the PR to duplicate the chromium expressions. The maintenance workflow will be to start with copy/pasted chromium expressions, then reapply the ungoogled-chromium expression diff on top of that, then update the ungoogled-chromium sources as needed. Ideally I wouldn't need to modify the copy/pasted chromium expressions at all, instead just naively duplicate them and keep the patchset-related stuff in separate files. However, I couldn't figure out any way to do that with the current chromium expressions. What I would need is the ability to externally (through an override maybe) provide extra gnFlags and add extra postPatch steps. |
@squalus Any update on your work on a separate package? I'd love to have Ungoogled chromium available for NixOS. |
@LouisDK1 Yeah, in the latest update to this PR there's a separate |
Awesome. I differently think this should get into the main repo. |
@squalus - Please update package to: 79.0.3945.130-2 and if possible change the headline to match the fact that this is a separate package. |
@LouisDK1 Updated the title, and left the version as-is. For now I'm aiming for the smallest possible diff from the "upstream" chromium nix expressions. I'll leave the testing and stabilization of new versions up to them. |
@ivan He has done it. Could you review and maybe accept the package? :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we not call it chromiumUngoogled
it's really backwards?
ungoogled-chromium
makes more sense https://repology.org/project/ungoogled-chromium/versions.
(and please rename the directories)
@squalus ping |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've built ungoogled-chromium and it works ✨
@worldofpeace Do you feel that the changes you requested were sorted? Your review is still marked as requesting changes 🙂 |
Works for me 👍 Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I don't feel I could properly commentate on adding another chromium flavor in nixpkgs other than it works. I don't completely approve of the maintainability of completely duplicating the chromium expressions. But I would be happy to use this. |
@worldofpeace Yeah, agreed. It would be great if some more of the common parts could be abstracted out of these packages. I'm inclined to merge as-is, though, since I suppose that would be a job too large for this PR. |
It was actually suggested #76082 (review). |
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/nixos-20-03-feature-freeze/5655/28 |
@worldofpeace - can you "accept" your request as it has been fulfilled? |
I compiled this PR successfully. |
@worldofpeace the changes you requested were fixed. Could we get the patch merged, pretty please? :( |
My delayed opinion (disclaimer: probably not really constructive, feel free to skip)
tbh I'm not sure if #76082 (review) was a good idea (cop-pasting the Chromium expression instead of overriding it) because:
But at least it doesn't make maintaining But I'm too late with this comment (sorry about this delayed note) and who knows, it might be better the way it is anyway. @squalus I'd suggest the following to maintain this (I'm the current
Also: Thanks for adding this package and good luck! I'm looking forward to a successful cooperation :) |
Thanks for merging! @primeos thanks for the comments. I have some maintenance scripts that will do this process semi-automatically. I'll commit them if I can make them look sensible. My plan for maintenance is just to periodically take the entire chromium directory, blindly copy it over, and apply the small set of ungoogled diffs. I would also like to work on the chromium expressions to make this process easier. 👍 No need to notify me over changes, I'll be periodically monitoring them (but feel free). I'm also looking forward to working with you! |
@danielfullmer Will do. Thank you! |
Motivation for this change
Adds support for the ungoogled-chromium patch set to the nixpkgs chromium derivation. Requested in #53579.
ungoogled-src.nix
file, which maps a chromium version to a ungoogled-chromium revision (although it's not able to be auto-updated likeupstream-info.nix
).The patch set can be enabled with the following nixpkgs config:
I'm very interested in feedback!
Prior work: #51195.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)Notify maintainers
cc @bendlas @ivan @thefloweringash