@blennow not everyone is using Plasma. E.g. I am a dwm user. Maybe you can install those packages by hand?
Search Criteria
Package Details: brave-bin 1:1.73.91-1
Package Actions
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: | 820 |
Popularity: | 16.85 |
First Submitted: | 2016-04-06 13:16 (UTC) |
Last Updated: | 2024-11-20 18:19 (UTC) |
Dependencies (8)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libxss
- nss (nss-hgAUR)
- ttf-font (neuropol-ttfAUR, ttf-win7-fontsAUR, ttf-ms-win8AUR, ttf-ms-win8-arabicAUR, ttf-ms-win8-hebrewAUR, ttf-ms-win8-seaAUR, ttf-ms-win8-indicAUR, ttf-ms-win8-japaneseAUR, ttf-ms-win8-koreanAUR, ttf-ms-win8-zh_cnAUR, ttf-ms-win8-zh_twAUR, ttf-ms-win8-thaiAUR, ttf-ms-win8-otherAUR, ttf-kidsAUR, ttf-liberation-sans-narrowAUR, ttf-cavafy-scriptAUR, ttf-ms-fontsAUR, ttf-dejavu-ibAUR, ttf-zeldaAUR, ttf-oxygenAUR, ttf-oxygen-gfAUR, ttf-share-gfAUR, ttf-gostAUR, otf-inconsolata-dzAUR, ttf-d2codingAUR, ttf-agaveAUR, ttf-caracteresAUR, ttf-cuprumAUR, ttf-autour-oneAUR, ttf-impallari-milongaAUR, ttf-impallari-miltonianAUR, ttf-clarity-cityAUR, ttf-ms-win10AUR, ttf-ms-win10-japaneseAUR, ttf-ms-win10-koreanAUR, ttf-ms-win10-seaAUR, ttf-ms-win10-thaiAUR, ttf-ms-win10-zh_cnAUR, ttf-ms-win10-zh_twAUR, ttf-ms-win10-otherAUR, ttf-win10AUR, ttf-ms-win10-cdnAUR, ttf-bmonoAUR, ttf-pt-astra-factAUR, ttf-weblysleekuiAUR, ttf-pt-astra-sansAUR, ttf-pt-astra-serifAUR, ttf-pt-sansAUR, ttf-pt-serifAUR, ttf-pt-monoAUR, ttf-pt-root_uiAUR, ttf-xo-fontsAUR, noto-fonts-liteAUR, ttf-paratypeAUR, ttf-plemoljp-binAUR, ttf-dejavu-emojilessAUR, noto-fonts-variable-liteAUR, ttf-lucida-fontsAUR, ttf-plemoljpAUR, ttf-juiseeAUR, ttf-ms-win10-autoAUR, ttf-karlaAUR, noto-fonts-latin-greek-cyrillicAUR, apple-fontsAUR, ttf-noto-sans-vfAUR, ttf-noto-serif-vfAUR, ttf-noto-sans-mono-vfAUR, ttf-ms-win11AUR, ttf-ms-win11-japaneseAUR, ttf-ms-win11-koreanAUR, ttf-ms-win11-seaAUR, ttf-ms-win11-thaiAUR, ttf-ms-win11-zh_cnAUR, ttf-ms-win11-zh_twAUR, ttf-ms-win11-otherAUR, ttf-ms-win11-autoAUR, gnu-free-fonts, noto-fonts, ttf-bitstream-vera, ttf-croscore, ttf-dejavu, ttf-droid, ttf-ibm-plex, ttf-input, ttf-input-nerd, ttf-liberation)
- cups (cups-gitAUR, cups-gssapiAUR) (optional) – Printer support
- libgnome-keyring (optional) – Enable GNOME keyring support
- libnotify (libnotify-gitAUR) (optional) – Native notification support
Required by (10)
- brave-extension-bitwarden-git (requires brave) (optional)
- chromium-material-icons-for-github-bin (requires brave) (optional)
- chromium-vencord (requires brave) (optional)
- chromium-vencord-bin (requires brave) (optional)
- chromium-vencord-git (requires brave) (optional)
- ice-ssb-git (requires brave) (optional)
- mermaid-cli-brave (requires brave)
- mermaid-cli-brave (requires brave) (make)
- nfauthenticationkey (requires brave) (optional)
- profile-sync-daemon-brave (requires brave) (optional)
Sources (4)
Latest Comments
« First ‹ Previous 1 .. 17 18 19 20 21 22 23 24 25 26 27 .. 59 Next › Last »
Iwirada commented on 2021-08-31 20:00 (UTC)
alerque commented on 2021-08-31 19:48 (UTC)
@blennow Add what exactly? This package is just a repackage of a binary build released upstream, modified only enough to fit in a PKGBUILD according to Arch packaging.
blennow commented on 2021-08-31 19:35 (UTC)
Hi, is it possible to add kdialog and kwallet to integrate with Plasma better? Maybe add plasma-browser-integration also.
francoism90 commented on 2021-08-19 07:57 (UTC)
Anyone else having these issues:
gnome-shell[7018]: [7018:7018:0819/095339.086798:ERROR:shared_context_state.cc(73)] Skia shader compilation error
Think it's caused by the VA-API enabled flag. :/
alerque commented on 2021-08-13 09:24 (UTC)
@zerophase You can't get fresh adblock lists for one. Please take that conversation to the relevant package though, it isn't an issue with this -bin package.
zerophase commented on 2021-08-13 03:11 (UTC) (edited on 2021-08-13 03:13 (UTC) by zerophase)
@alerque What extensions can't run in unofficial builds? Couldn't we just fork the extensions, and enable them?
alerque commented on 2021-08-12 19:02 (UTC)
@srebre It's not an easy as just getting votes. This package is just the upstream binary, for the repos we'd really want to build it ourselves. The brave PKGBUILD does that, but there are other complications (see comments there): Brave Inc. is not letting some extensions run in unofficial builds, plus building it is quite a procedure. That brings us into needing to negotiate license/distribution issues.
I am a TU and have my eye already on moving this to [community] if we can navigate all those dealt with, but don't expect it any time soon. In the mean time using this is your best bet for a working browser (but be aware you're trusting a binary blob built by a for-profit Browser vendor).
srebre commented on 2021-08-12 18:01 (UTC) (edited on 2021-08-12 18:04 (UTC) by srebre)
Since this package has 400+ votes, can we integrate it into the official repositories and who should we reach out to? It's the third most popular package by votes in AUR at the time of writing.
alerque commented on 2021-08-06 17:36 (UTC)
@alosarjos Yes, if it's deprecated we should be pointing the current dependency, optional if it is so. I don't let my browsers or DE session handle secrets, so I'm a little out of that loop. Feel free..
alosarjos commented on 2021-08-06 16:42 (UTC)
@alerque, now that the update thing is gone, the package has libgnome-keyring as optional depdency, which is deprecated for libsecret I think. Should that dedepency be changed?
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.