Also, I'd build it on a minimal Void installation with no dbus, just to have a very clean build environment that's already got some similarities to Hyperbola. You can have a graphical environment with void without any dbus if you stick to DWM (or probably JWM as well). I can walk you through the Void setup steps. I'll try building it soon. I may not have time to dig into it right away this week, but maybe the week after.

If I do get it built, I will need some help from you, zapper, on my Hyperbola 0.4 installation so I can test out the Firefox binary. I've had a bit of trouble with my graphics setup, and have set it aside and didn't bother to figure it out yet.

I recommend looking into LibreWolf instead of {{{Firefox}}}

LibreWolf appimage works on Dev1 5.16.0-6 and the previous stable v4 iso also

LibreWolf works with ALSA out of the box also

I am familiar with Arch packaging. My instructions in post #9 should work.

See https://wiki.archlinux.org/title/Arch_B … _using_Git for a quick way to checkout the Firefox PKGBUILD from the Arch repositories.

Only problem is Hyperbola has no rust,  with which to build it from...

Also, glibc version from Hyperbola is too old to work with  any builds from Arch.

See https://wiki.archlinux.org/title/Arch_B … _using_Git for a quick way to checkout the Firefox PKGBUILD from the Arch repositories.

You won't be able to run a Devuan binary in Hyperbola. The ABI will be different and the sonames won't match.

hmm...

huh...

I may just need to talk to one of my hyperbola buddies, he seems to know how to do stuff like this, I reckon I will have to wait for him.

Perhaps this is too complicated for me on my own... oh well...

I was going to build with ./mach package after build succeeded, but oh well.

Edit: I guess I should have had the title say from Devuan. That was more what I meant...

here's what I did. from git,

installing firefox from git

archived :  /home/glenn/local/archive/src/apt/SOURCES/firefox-93.0.tar.bz2

cd /opt
wget https://download-installer.cdn.mozilla.net/pub/firefox/releases/93.0/linux-x86_64/en-US/firefox-93.0.tar.bz2
tar xfj firefox-93.0.tar.bz2
/opt/firefox/firefox
remove the old firefox links
mv /usr/bin/firefox /usr/bin/firefoxold
or after backup of bookmarks and passwordz
apt remove firefox-esr
create new link
ln -s /opt/firefox/firefox /usr/bin/firefox

Works for me, I hope it works for you.

I have no idea what this is...

I am trying to compile firefox with a modified config to be more secure and not require dbus, so I can use it on Hyperbola.

Also, with alsa support and no libpulse dependency, etc...

This doesn't make sense to me

Can you explain?

installing firefox from git

archived :  /home/glenn/local/archive/src/apt/SOURCES/firefox-93.0.tar.bz2

cd /opt
wget https://download-installer.cdn.mozilla.net/pub/firefox/releases/93.0/linux-x86_64/en-US/firefox-93.0.tar.bz2
tar xfj firefox-93.0.tar.bz2
/opt/firefox/firefox
remove the old firefox links
mv /usr/bin/firefox /usr/bin/firefoxold
or after backup of bookmarks and passwordz
apt remove firefox-esr
create new link
ln -s /opt/firefox/firefox /usr/bin/firefox

Works for me, I hope it works for you.

ps. no compiling ;-)

I had thought that as well, but it still seems to not pass on my changes, which is very weird imo.

Look in the debian directory inside the firefox-esr source, the browser.mozconfig.in file is the one you want.

zapper wrote:

[how the hell do I get the ./mach build to use the mozconfig changes I made?

Follow the instructions on the BLFS page to which I linked.

Or just add a line to the PKGBUILD prepare() function and run makepkg -sri to build and install the custom package if you're doing this from Hyperbola.

I was using the apt source version from devuan, I am a bit confused and kind of annoyed... also, I am using devuan currently to build.

Also, I should add for more info, all I really need is to know which mozconfig, etc.. to modify to add my changes.

[how the hell do I get the ./mach build to use the mozconfig changes I made?

Follow the instructions on the BLFS page to which I linked.

Or just add a line to the PKGBUILD prepare() function and run makepkg -sri to build and install the custom package if you're doing this from Hyperbola.

The .js preferences files work with any version of FF. You don't have to compile a custom version to use them.

That is good, but tell me something, how the hell do I get the ./mach build to use the mozconfig changes I made?

It keeps doing the same old crap, no matter what I do.

It effectively acts like I changed nothing! Its kind of infuriating...

Very much so...

I mean, all I want is to do things a specific way, and to compile with less than 4 cores, and the damn thing refuses to accept my config for building.

This is my mozconfig in, browser/config/mozconfig

It feels almost like the devuan/debian build is meant to sabotage modifications... unless I am mistaken...

but yeah, its annoying.

I dont know anything on compiling FF but i use arkenfox user.js with a custom user-overrides.js

arkenfox github page has all the instructions you need.

https://github.com/arkenfox/user.js

and this for the user-overrides.js that i have edited for my own personal use.

https://codeberg.org/12bytes.org/Firefo … supplement

Does it work before or after its compiled?