Second Opinion Required: Brave Web Browser Command Terminal Installation Instructions

South Paw

New Member
Joined
Dec 12, 2023
Messages
3
Reaction score
2
Credits
42
Background Info: I am new to Linux. I recently installed Linux Lite OS 7.0 which is based on Debian and Ubuntu (More Info: https://distrowatch.com/table.php?distribution=lite) I recently starting using brave web browser on my phone and signed up for Brave Rewards. It's something new so I figured "Why not?". I did my research on Brave Browser before downloading it on my phone of course, and I have been wanting to install it on my laptop ever since. The "issues" began when looking into the terminal instructions for installing brave web browser.

Issue: I was looking up instructions for how to install Brave Web Browser on my laptop using the terminal. I went to the developer site first (https://brave.com/linux/#release-channel-installation). I also attached a screen shot of the instructions on the Developer's Website. For some reason, I started wondering to myself if there are few steps the developer's are "leaving out" under the subsection of Debian, Ubuntu, & Mint under the Release Channel Installation instructions section.
Thus, I began looking at other links. Specifically:

1. https://itsfoss.com/brave-web-browser/
2. https://www.makeuseof.com/how-to-install-brave-browser-linux/
3. https://www.fosslinux.com/46604/install-brave-web-browser-linux.htm
4. https://linuxiac.com/how-to-install-brave-browser-on-linux/

While looking under the instructions pertaining to terminal commands for Debian and Ubuntu based distributions, I began seeing slight variations in of the steps on each website. Several things come to mind when contemplating this issue. Are the variations in the terminal command steps because of different versions of different Debian and Ubuntu based distributions? Is it just specific preferences of commands used during the installation process by the authors? Am I overthinking things again and should just use the steps on the developer's website for brave? Are there certain things that authors of the other four web articles have on their Linux systems that I do not, which is why there are slight variations in the steps provided in the other web articles? Do the developers of Brave leave out certain commands intentionally because people have different distributions that are be based on Debian and Ubuntu and there are "different strokes for different folks" that I am ignorant to? I need some clarification because it seems to me that there subdivisions of beginners, and for some reason I feel as though I fall under the category of a "beginner beginner" (or rather the cavemen of cavemen) if you catch my drift.
 

Attachments

  • Brave Installation Instructions.png
    Brave Installation Instructions.png
    127.7 KB · Views: 131


Or just download the AppImage. You want the file: Brave-stable<blah-blah-version>-x86_64.AppImage

If you don't know about AppImages:
AppImages are better for isolation and you don't end up with excess gunk in sources.list. For those still living in the 2000s, AppImages are compressed filesystems that provide all dependencies and allow universal Linux apps at the expense of storage and a little overhead. Pros are they can easily be jailed, they're portable, and there's no installation, just chmod +x YourApp.AppImage and run. Place them in .local/lib and add a shortcut to .local/bin if you want to feel like you installed them for just you, or for system-wide, in /opt/<name-of-app>/ (chmod a+x in this case) and link to /usr/local/bin/<app name>

My opinion specific to your question: Always follow upstream's instructions. They're the devs.
My not-so-humble opinion about third-party vendors: Don't add repos to sources.list. Look for an AppImage. If there's no AppImage, and if you're willing to add repos, then rather use (edit: meant flatpak). I don't care for it, but it provides something similar to Python's pip. TBH: I just don't use things outside my repo that I cannot get AppImages or the source code for (and with the latter, it needs to be well-audited source) -- well, on my PC, my laptop's now dedicated to work and running Edge so I can use O365 because even Chrome breaks Office Online. As a rule, don't go outside if you want to avoid mud on your shoes.
 
Last edited:
Or just download the AppImage. You want the file: Brave-stable<blah-blah-version>-x86_64.AppImage

If you don't know about AppImages:
AppImages are better for isolation and you don't end up with excess gunk in sources.list. For those still living in the 2000s, AppImages are compressed filesystems that provide all dependencies and allow universal Linux apps at the expense of storage and a little overhead. Pros are they can easily be jailed, they're portable, and there's no installation, just chmod +x YourApp.AppImage and run. Place them in .local/lib and add a shortcut to .local/bin if you want to feel like you installed them for just you, or for system-wide, in /opt/<name-of-app>/ (chmod a+x in this case) and link to /usr/local/bin/<app name>

My opinion specific to your question: Always follow upstream's instructions. They're the devs.
My not-so-humble opinion about third-party vendors: Don't add repos to sources.list. Look for an AppImage. If there's no AppImage, and if you're willing to add repos, then rather use (edit: meant flatpak). I don't care for it, but it provides something similar to Python's pip. TBH: I just don't use things outside my repo that I cannot get AppImages or the source code for (and with the latter, it needs to be well-audited source) -- well, on my PC, my laptop's now dedicated to work and running Edge so I can use O365 because even Chrome breaks Office Online. As a rule, don't go outside if you want to avoid mud on your shoes.
Thanks. This helps.
 


Staff online


Top