What they fail to mention is the above three alternatives maybe because its not recommended by them (I wouldn't know) or maybe because they don't know these are options. These reasons are rather good, and we are ever so thankful for their efforts with maintaining the madhouse that is the repos after all. The developers are somewhat hostile to using build-server infrastructure to build any additional forks of Chromium or Firefox, as well as generally citing more variable reasons with the former ranging from patched code to the difficulty of packaging a browser and followed by warnings to those who would maintain (and cross compile) the thing. Why It Will Not Be in the XBPS Repos Anytime Soon I have tried both 2&3 personally, tested the browser functions and then uninstalled it as I have 0 desire to use it for anything (and it looks awful with my GTK theme) due to using a heavily modified (CSS & JS) Firefox. deb of Brave found here to a xbps package which the utility spits out a command for you to copy-paste to install it. Using the utility script xdeb located here to convert the. (Note: will be isolated from the system which can be a bit of a pain, especially using things like keepassxc) Use flatpak, which I need not explain since instructions are on the flathub listing itself. There are three methods that I am aware of:Īdd this template file to your fork of void-packages locally and build the. Yes, you can relatively easily install brave browser on void linux, if that is somehow a non-negotiable for you fear not.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |