Distribution packaging questions

[zeroability]

Hello everyone.

It's my first time here, but I remember the old days of Mozilla and Netscape. I'm working on packaging this for OpenMandriva Lx, and have some questions.

I already sent a PM to Basilisk-Dev about branding, but I don't know if I need to make posts before PM's can be sent. It wouldn't let me search for users to add, so I would assume so. I have a successful build with the Snake branding but it looks like the Basilisk branding is behind a registration wall. What do you require of us to brand it appropriately?

Is there a config option to turn off auto update? We would obviously just like to build with the new version that comes out from the git repos.

Thank you for the help in advance.

[Basilisk-Dev]

PM Sent.

Add this to your mozconfig:

Code: Select all

ac_add_options --disable-updater

[zeroability]

Can I pass it as an export, or do I need a full .mozconfig?

[Moonchild]

You need a .mozconfig, although you can tell the build system to use a specific .mozconfig with an export:

Code: Select all

export MOZCONFIG=/path/to/.mozconfig

[Basilisk-Dev]

Can I pass it as an export, or do I need a full .mozconfig?

If it helps there are sample mozconfigs in the repo. See https://repo.palemoon.org/Basilisk-Dev/ ... figs/linux

[zeroability]

Does it still just need to reside in the root of the source/repo?

[Moonchild]

Does it still just need to reside in the root of the source/repo?

You can put it there or see my previous post (i always build that way, myself, to be explicit whic config is used without having to shuffle files around)

[zeroability]

That makes sense. Our distro uses rpm, so I need to move a file around, anyway. I can just include a config as a source and it does the rest.

[zeroability]

For anyone interested, I was able to create a working spec file (well, BD hasn't told me it's trash, yet ). I am currently testing a local build with somafm[dot]com audio playback with their web player. So far, so good (unless I'm compiling but I don't think that is the fault of Basilisk). Bitwarden doesn't quite render correctly, but I'm willing to work around that limitation.

[zeroability]

Basilisk has been accepted into our Cooker (testing) release.