Brave Origin in the official repo?

[GuyOthersome]

Any idea if/when Brave Origin could make its way into the official CachyOS repo? Would it depend on being available in the standard Arch repo first?

Brave Origin is a stripped-down version of the standard Brave browser that removes the crypto and Leo AI features but keeps the ad-blocking and ManifestV2 compatibility. Right now it’s only available as a nightly build for free on Linux, but costs $60 for a permanent(!) license for macOS and Windows. It’s in the AUR as brave-origin-nightly-bin and brave-origin-beta-bin.

[cscs]

@GuyOthersome

Any idea if/when Brave Origin could make its way into the official CachyOS repo?

If the maintainers decide to do it.

Going by previous decisions it will depend largely on if there is some sort of desire and an existing bin build.

The AUR examples already shown are bins so theres that.

Though I do already think theres a good number that we could do without and that more scrutiny on them is probably needed. While personally I do not like brave so there would be no interest from me.

@GuyOthersome

Would it depend on being available in the standard Arch repo first?

No.
That would mean we would get it, yes .. but thats not very likely.
The regular brave is not in the Arch repos.

[CacheMeIfYouCan]

@cscs

While personally I do not like brave

Not only that, but it is a very controversial software on many levels…

Maintaining a binary package requires ensuring it’s always current with the latest security updates… so it’s a duplication of effort… and much more so for a nightly build.

[neveS]

Wouldn’t bother with AUR - the lazy and riskier way, when the official install works just fine:

curl -fsS https://dl.brave.com/install.sh | FLAVOR=origin CHANNEL=beta sh

…like a charm. And thus, nightly becomes an Optional channel (you can always opt for beta - as shown above). As shown here: Installing Brave Origin Beta on Linux | Brave

Point being, you already know it works - since standard Brave is already available and almost fully functional. So Brave Origin works just the same. It’s not like someone obscure (unknown or less known) app. Won’t make much of a difference if included in official CachyOS repo. Maybe just for Linux beginners - who are afraid of using the CLI and only trust the GUI installer, but if that’s the case - they picked the worst Linux distro (CLI is a must - while using any Arch based distro). In all honesty - would be completely lost without it. What other option is there - to keep reverting the back-up image or reinstall it after every issue one encounters (minor or critical)?

[CacheMeIfYouCan]

@neveS

Wouldn’t bother with AUR

Some people prefer to be lazy than to spend an hour or three trying to compile a browser - what’s wrong with getting the official brave-origin-beta-bin from AUR?

Name: brave-origin-beta-bin
Upstream URL: Brave Origin Beta Download | Brave
Votes: 5
Popularity: 3.82
Version: 1.91.143-2
Size: 0 B
Description: The minimalist browser from the makers of Brave (beta binary release).
First Submitted: 2026-04-13 20:48:21 (UTC)
Last Updated: 2026-05-07 12:59:09 (UTC)
Link: AUR (en) - brave-origin-beta-bin

[dennis1]

@neveS

Wouldn’t bother with AUR - the lazy and riskier way

Official site literally recommends AUR to Arch users, and PKGBUILD also looks like it’s maintained by the upstream devs.

[CacheMeIfYouCan]

The pkgbuild - looks legit…

Also, if you ‘curl’ it in today, how will you figure out how to uninstall it later down the line?

# Maintainer: brave-prerelease <aur-prerelease@brave.com>

pkgname=brave-origin-beta-bin
pkgver=1.91.143
pkgrel=2
pkgdesc='The minimalist browser from the makers of Brave (beta binary release).'
arch=(x86_64 aarch64)
url='https://brave.com/origin/download-beta'
license=('MPL2')
depends=('gtk3' 'nss' 'alsa-lib' 'libxss' 'ttf-font')
optdepends=('cups: Printer support'
            'mesa: Hardware accelerated rendering'
            'libglvnd: Support multiple different OpenGL drivers at any given time'
            'libgnome-keyring: gnome keyring support')
provides=("${pkgname}" "${pkgname%-bin}")
conflicts=()
source=("$pkgname.sh")
options=(!strip)
source_x86_64=("https://github.com/brave/brave-browser/releases/download/v${pkgver}/${pkgname%-bin}_${pkgver}_amd64.deb")
source_aarch64=("https://github.com/brave/brave-browser/releases/download/v${pkgver}/${pkgname%-bin}-beta_${pkgver}_arm64.deb")
sha512sums=('d29202fe9c1433cc70f2f8032c1d3c8d61d4eac88324c4ddd475f59ce9198e1ff6b6ec2c6005e932960dda83439aae5092251c7dd90321c91b9775b31c4f5d51')
sha512sums_x86_64=('925d0a227f7ba6e7c86b85bfb83e02d583243630478d90fdf32a8c747bcb82651d6fffcd2839c99fae6e3bf0025fae7e8bef9b30bdf36238b7f5408f9c4f751f')
sha512sums_aarch64=('e9810dc1d3faab1402f85f2b5013ccc7002301878aa6b512fa4499b6c11285c6ba19ca16b0941cbec9a9f9da4faec6c1de3ec5a690ee4ccf94fdb51d5a6fea52')

prepare() {
  mkdir -p brave
  tar -xf data.tar.xz -C brave
  rm -rf "brave/opt/brave.com/${pkgname%-bin}/cron"
}

package() {
    cp -a --reflink=auto brave/opt "$pkgdir/opt"
    cp -a --reflink=auto brave/usr "$pkgdir/usr"
    rm -f "$pkgdir/usr/bin/${pkgname%-bin}"
    install -Dm0755 "$pkgname.sh" "$pkgdir/usr/bin/${pkgname%-bin}"
    install -Dm0644 "brave/opt/brave.com/${pkgname%-bin}/product_logo_128_beta.png" "$pkgdir/usr/share/pixmaps/${pkgname%-bin}.png"
    install -Dm0664 -t "$pkgdir/usr/share/licenses/$pkgname" "brave/opt/brave.com/${pkgname%-bin}/LICENSE"
    chmod 4755 "$pkgdir/opt/brave.com/${pkgname%-bin}/chrome-sandbox"
}

[neveS]

@CacheMeIfYouCan

Some people prefer to be lazy than to spend an hour or three trying to compile a browser - what’s wrong with getting the official brave-origin-beta-bin from AUR?

In this case, curl takes same amount of time - if not less.

@CacheMeIfYouCan

Also, if you ‘curl’ it in today, how will you figure out how to uninstall it later down the line?

First - just to be sure, you find the exact naming:

pacman -Q | grep -i brave

Which in this case is: brave-origin-beta-bin

Followed by the usual:

sudo pacman -Rns brave-origin-beta-bin

Which again, doesn’t take longer than uninstalling the other versions. As mentioned above, standard version was already included in official repos - while this one is not much different - even less than that - since it’s stripped down. It’s not like they added extra function - requiring extra dependencies. In this specific case - the AUR lazzy way doesn’t cut it (no benefits - you did more work verifying the pkbuild yourself).

[neveS]

@dennis1

Official site literally recommends AUR to Arch users, and PKGBUILD also looks like it’s maintained by the upstream devs.

That’s Not a recommendation. That’s an OPTION (the only one - currently… the Arch way). curl is also an/other option. Recommendations - come with a justification - why that’s the recommended way. Maybe if eventually it’s added and maintained by an official repo - then yes, than can be taken as a recommendation. As it’s usually the case - vs using AUR.

Just look around - so many new/beginners users taking AUR so lithely - even pushing latest Kernels available through AUR - only to brake some core functionality or CachyOS booting - with some update.

AUR is the Arch way… “FOR ADVANCED USERS” - who are used to braking, fixing and reverting to a working snapshot.

Keeping AUR - as optional even for Shelly’s default settings - was the reasonable choice (yet, so easy to enable), for this exact reason - i presume.

[mattsteg]

@neveS

That’s Not a recommendation. That’s an OPTION (the only one - currently… the Arch way). curl is also an/other option.

you do realize that script just uses an AUR helper to install from the AUR, right?

And it uses a non-recommendable / unsafe command to do so (i.e. yay -Sy)

@neveS

only to brake some core functionality or CachyOS booting - with some update.

Brave is literally doing one of the things that can commonly lead to this sort of thing

A user is far better off installing independently through an AUR helper implementing well-known best practices.

[CacheMeIfYouCan]

@mattsteg

A user is far better off installing independently through an AUR helper implementing well-known best practices.

I’ve discussed this in the past - with someone explaining to me that they’re just not clever enough to understand the pkgbuilds, so they ‘just install’.

The interesting thing is - they are members of the forum… and there are dozens of folks here who would instantly respond if you pasted a pkgbuild here and asked about it…

Additionally, ‘traur’ is interesting (not reliable, but it can bring up potential red flags).

In some ways, I’ve noticed many Cachy users tend to be more like Windows users than Linux users… 'whatever works, who cares about ‘best practices’?

I’m not the sharpest tool in the box - but I generally just go along with ‘yay’ or ‘paru brave-origin’ and let the search bring me options, then I choose my option… obviously safety depends also to some degree how your paru/yay settings are looking.

[mattsteg]

@CacheMeIfYouCan

In some ways, I’ve noticed many Cachy users tend to be more like Windows users than Linux users… 'whatever works, who cares about ‘best practices’?

It’s a very popular distro with new users. A lot of them are Windows users.

Managing application distribution and trust is a hard problem. There isn’t really a great solution that scales to everything.

And even “professionals” like Brave give instructions to install their software with a command that the Arch Wiki says to never use.

[neveS]

@mattsteg

you do realize that script just uses an AUR helper to install from the AUR, right?

And it uses a non-recommendable / unsafe command to do so (i.e. yay -Sy)

Exactly, you’ve just proven my point.

@mattsteg

Brave is literally doing one of the things that can commonly lead to this sort of thing

A user is far better off installing independently through an AUR helper implementing well-known best practices.

Depends… if you trust Brave Software - as being a legitimate (trust-worthy - unlikely to act maliciously), competent, security-conscious brand. Or Not. Maybe you don’t - based on your given response. But being such a popular app - which many users trust to the extent - of using their Credit Card details…i can admit that i trust the vendor and their given script - even without inspecting their curl | sh After all, it’s quite transparent (not some obscure script from an obscure site - which i wouldn’t even bother trying let alone waste time checking its legitimacy). Brave even provides signature verification instructions and source visibility.

[mattsteg]

@neveS

Depends… if you trust Brave Software

That’s not really the concern here, unless you want to make the argument that they, as a web browser company, know Arch better than Arch does.

They run and recommend a command that can break systems (in ways that have nothing to do with Brave’s browser and whether it’s good or trustworthy). Their installer leaves your package database out of sync with your installer. That’s bad. That can break the next piece of software that you install.

Trusting Brave to produce software I trust and trusting them to install it correctly on Arch are 2 very different things.

[cscs]

As has been noted elsewhere ..

The brave install script has partial-upgrades baked right in.

That means its not just garbage but actively harmful.

Not that it is unexpected of them but I would still say that if you must use their browser then still avoid their install script as it is fundamentally broken in the most basic way.

Brave (AUR brave-bin) cannot open PDFs

Brave showing off again that there are more reasons to doubt than to trust.. That script wont do anything special for you .. its going to try to install brave-bin from the repos if it exists or brave-bin from the AUR if not. Through a partial-upgrade. This is very much how not to do installs.. elif available pacman; then if pacman -Ss "brave-browser$dashCHANNEL" >/dev/null 2>&1; then show $sudo pacman -Sy --needed --noconfirm "brave-browser$dashCHANNEL" else …

As can be seen by the quotation above .. its also not new.

Whether you consider this as indicative of anything else with them or worth considering is maybe a personal matter.

But the browser they produce and their understanding of Linux/Arch packaging or system management are technically different things as mentioned by other comments in the thread.

[GuyOthersome]

Looks like brave-origin-bin is now in the cachyos repo.

[cscs]

Guess so.

It does seem like a better version of brave - by stripping out and/or allowing the user to disable various things it does to generate revenue - “Rewards”, “Brave Ads”, “Product Analytics”, etc.

( Again such normal things for a privacy-first browser to have.. )

Though you have to purchase a license for these premium features (the feature being the ability to opt out of those advert+ things).

Still all gives me the ick but its there for folks who want it.

[triam]

@cscs

Though you have to purchase a license for these premium features (the feature being the ability to opt out of those advert+ things).

You don’t need to purchase a license on Linux for brave-origin. You can, if you want to support the project. Moreover, in regular Brave Browser you can disable unwanted features and telemetry from the settings or via policies (e.g. brave-debloater/policies.json at main · Anxarden/brave-debloater · GitHub). You can achieve this on Windows as well (https://support.brave.app/hc/en-us/articles/360039248271-Group-Policy), and they explain how!

Mozilla Firefox’s engine has a very narrow market share it is often slower, and not every webpage works well or is optimized. Manifest V3 is very close, so there will be less effective ad-blocking on Chromium-based browsers soon. Smaller projects—forks of forks (e.g. Helium, a fork of Ungoogled Chromium, which is itself a fork of Chromium)—may be delayed in the case of a zero-day exploit. I feel safer with imperfect Brave.

[cscs]

Interesting that its $60 for everyone else but free for linux users.

But regardless of any of that does not this version existing and its features all sort of give credence to the myriad former - and oft chafed - criticisms of brave? If you need this version to not have “brave-ads” and so on then what does that say about the original - despite what was often claimed?

And they still do not understand partial upgrades and continue to use/suggest them;

https://imgur.com/0mnRQZB

yay -Sy brave-origin-bin

https://brave.com/origin/linux

[Dagrod]

@cscs

Interesting that its $60 for everyone else but free for linux users.

But regardless of any of that does not this version existing and its features all sort of give credence to the myriad former - and oft chafed - criticisms of brave? If you need this version to not have “brave-ads” and so on then what does that say about the original - despite what was often claimed?

And they still do not understand partial upgrades and continue to use/suggest them;

What’s the alternative, anyway, that painfully slow Firefox, where websites are sometimes displayed incorrectly, layouts get messed up, and it regularly freezes while loading pages? Where every new version just adds more unnecessary bells and whistles that you then have to go through the trouble of removing? Among the Chromium-based browsers, Brave is simply the only real contender thanks to its built-in, excellent ad blocker.