What is the current position of void-packages maintainers on Brave browser package?

[vulpes-vulpeos]

I remember reading that Void maintainers try to avoid forks, so no Chromium forks are allowed if Chromium itself is available (Vivaldi and Opera were added before this rule). Chromium isn’t the best choice now due to Manifest V3, which makes many extensions unavailable — they're still in the store, but the install button is inactive.

It’s possible to install the Brave browser via xbps-src, and it allows installation of any extensions (Manifest V2 is still supported).

So the question is: will the Brave browser package be allowed because of Manifest V3, or are there other reasons why it won’t be added to the void-packages repo?

[classabbyamp]

the browser fork policy still applies

(also it's a crypto scam)

[vulpes-vulpeos]

I spent some additional time googling, and it seems that all Chromium based browsers will drop support for Manifest V2 — either the V2 code will be removed from chromium sources, or V2 extensions will be taken down from the extension store.

Also rechecked my extensions, and all of them work with V3, so Chromium is still a viable option for me. The only extension I had to replace was uBlock Origin: I installed uBlock Origin Lite and moved my custom filters to the Stylus extension.

[gc-user]

This discussion got me searching, too.

Found this:

ExtensionManifestV2Availability
https://chromeenterprise.google/policies/#ExtensionManifestV2Availability

How to keep using adblockers on chrome and chromium
https://gist.github.com/velzie/053ffedeaecea1a801a2769ab86ab376

Chrome for Linux: a policy to enable Manifest V2 and force enable DNS over HTTPS using CloudFlare's one.one.one.one server
https://gist.github.com/birdie-github/d09d1c38bf4e1faa0b929093d75a3349

I'll try this with vivaldi. Otherwise I'll just compile it myself using a patch I found to reactivate V2...

Update:

Here's a better source to tackle this issue for vivaldi:

https://forum.vivaldi.net/post/785135

The main issue for me was the wrong directory / path that some links provide.

The policy file (.json) has to be in /etc/chromium/policies/managed for vivaldi to find / recognize it.
Any other place like /opt/..., /etc/opt/... or /etc/chrome doesn't work. With the correct directory the policy file is found instantly, not even a reload / re-check of the policies (vivaldi:policy) needed.

But I'm not sure if this is even necessary for vivaldi as I found this flag: #allow-legacy-mv2-extensions which seems to be enabled by default (?) and seems to do the same as the policy "hack".

[vulpes-vulpeos]

Vivaldi will drop v2 support: https://vivaldi.com/blog/manifest-v3-update-vivaldi-is-future-proofed-with-its-built-in-functionality/

We will keep Manifest v2 for as long as it’s still available in Chromium. We expect to drop support in June 2025, but we may maintain it longer or be forced to drop support for it sooner, depending on the precise nature of the changes to the code.

[gc-user]

Yeah, unfortunately. They should drop chromium base and go "back" to presto... :-)