@digitalone Thanks for the heads up, just uploaded the PKGBUILD without the .deb code.
As for Widevine support, Brave manages its own version and thus doesn't need the chromium-widevine package to work.
Git Clone URL: | https://aur.archlinux.org/brave-bin.git (read-only, click to copy) |
---|---|
Package Base: | brave-bin |
Description: | Web browser that blocks ads and trackers by default (binary release) |
Upstream URL: | https://brave.com |
Keywords: | brave browser |
Licenses: | BSD, MPL2, custom:chromium |
Conflicts: | brave |
Provides: | brave, brave-browser |
Submitter: | toropisco |
Maintainer: | alerque (alosarjos) |
Last Packager: | alosarjos |
Votes: | 843 |
Popularity: | 19.04 |
First Submitted: | 2016-04-06 13:16 (UTC) |
Last Updated: | 2025-02-13 20:10 (UTC) |
« First ‹ Previous 1 .. 41 42 43 44 45 46 47 48 49 50 51 .. 59 Next › Last »
@digitalone Thanks for the heads up, just uploaded the PKGBUILD without the .deb code.
As for Widevine support, Brave manages its own version and thus doesn't need the chromium-widevine package to work.
Generic Linux zip package has now resources folder included, so we can skip deb package downloading.
Besides, I made a new PKGBUILD with optional chromium-widevine support. Note that you don't have to install chromium to get chromium-widevine.
Installed and tested with a streaming service I use in my country: playback works smoothly (obviously you have to disable brave shield for that specific page). Should also work for Netflix, Amazon Prime and other streaming services.
I think it's because those files were copied manually before and pacman detects a conflict.
The last build failed for me because it didn't remove the old locale files at: /usr/lib/brave-bin/resources/brave_rewards/_locales/ and /usr/lib/brave-bin/resources/brave_extension/_locales/
run sudo rm -rf for each of them.
Thanks. Anyway, deb package uses Ubuntu directory schema that seems a little bit different from Arch's one. Brave primary folder is in /opt/brave.com/brave
rather than /usr/lib/brave-bin
. I don't know if this can cause any issue on Arch.
Hey guys, sorry I didn't respond earlier just saw the comments today and re-enabled notifications. So:
afontenot: Removed gconf from depends and moved libgnome-keyring to optional dependencies.
digitalone: Thanks for the reminder on pkgrel, I made the change on a machine without my usual pre-commit hook and didn't notice. Regarding the extension bug, I was looking into avoiding a second download of the browser just because of an upstream packaging issue; but since a lot of people use Brave solely for the crypto stuff I'll just merge those changes until I have more time to look into using the deb alone. Thank you for the patchset, just merged.
When you modify the PKGBUILD, you should also increase pkgrel number otherwise users that already installed the package won't get any change.
And, please, merge my modification reported here to include resources directory from deb release so Brave Shield issue can be fixed until developers will make a fully working linux zip package.
This PKGBUILD modified by me fixes Brave Shield issue. Please update.
Following up: I've been running an edited version of this PKGBUILD with libgnome-keyring and gconf removed from depends for a while with no problems under KDE. As I said in a previous comment, they're not required by the Debian brave package. Can you move them to optdepends please?
Pinned Comments
wknapik commented on 2025-02-06 18:10 (UTC)
alerque commented on 2021-11-27 03:11 (UTC)
@ant0n et all, lets keep the comments here about packaging issues, general Brave usage issues should go in another forum to not clutter up this comment space. I'm deleting comments that have no relation to packaging. Grey areas like crashes that could be blamed on Arch can stay until proven otherwise, but things like how to configure Brave to handle popups or site X or whatever just don't belong here. Thanks for understanding.