Package Details: brave-bin 1:1.74.51-1

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: 842
Popularity: 19.56
First Submitted: 2016-04-06 13:16 (UTC)
Last Updated: 2025-01-29 17:53 (UTC)

Dependencies (8)

Required by (10)

Sources (4)

Pinned Comments

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.

Latest Comments

1 2 3 4 5 6 .. 59 Next › Last »

alosarjos commented on 2025-01-29 17:56 (UTC)

@wknapik

If you want to write a message to be pinned for those looking for support (Not related to the packaging itself). Just write it and I will pin it :D

wknapik commented on 2025-01-29 17:54 (UTC)

@3a33d updating involves restarting the browser. Have you checked brave://settings/clearBrowserData to see if you have cookie removal enabled on exit?

3a33d commented on 2025-01-24 21:04 (UTC)

Whenever I go about updating brave, it seems my cookies reset. Would you happen to have any idea if there's something obvious that might be causing this?

IEatedASoup commented on 2024-11-12 01:35 (UTC)

When installing this via yay, the brave-bin-1.71.123-x86_64.zip does not pass sha256sum validation, and thus will not install.

melvilli commented on 2024-10-06 13:20 (UTC)

haha nice. no issues though. i didn't expect it to suddenly get flagged out of date for whatever reason even though the update was just a day late. Usually it isn't that fast, no?

alosarjos commented on 2024-10-03 14:54 (UTC)

I have a bot checking for updated every 24 Hours, please have some patience...

melvilli commented on 2024-10-03 13:16 (UTC)

Looks like it got flagged out of date? The current release is v1.70.123 released yesterday. Is the author dropping the packaging support or is it just a friendly reminder by the community?

tejohnso commented on 2024-09-16 14:10 (UTC)

wknapik I believe this is related to the complication you were referring to: https://github.com/brave/brave-browser/wiki/Build-configuration

I wonder how broken a completely keyless build would be. Looking at those parameter names, there are a number that seem to be less than critical.

wknapik commented on 2024-09-16 13:08 (UTC)

It's because Brave is not willing to give permission to Arch to distribute a version that they compile.

Let's clarify this a bit. Brave has no issue with binary redistribution/repackaging. However, packages in default Arch repos need to be built from source by Arch maintainers and that's where the complication lies.

To build a fully functional browser, that has access to all external services needed to provide the functionality, a number of secrets are needed at build time. Each of those secrets is tied to expenses, either in infrastructure run by Brave, or in access to paid external services used by the browser. For that reason, while the browser can be built from source by anyone, in practice, to get access to all those services, one needs to use pre-built binaries.

If a way can be found to avoid leaking those secrets, while being included in Arch's default repos, we could have this package in Arch, without having to use AUR.

1 2 3 4 5 6 .. 59 Next › Last »