Arch Linux User Repository

This split PKGBUILD provides a common way to generate an autoconfig.js policy, used for bringing user.js as default, system-wide configuration. This is especially useful for people who want to use official Firefox builds (e.g. to avoid AUR updates) or forks not bundling with user.js as default configuration or policy.

Take a note LibreWolf default configuration is a bit different from user.js and this script doesn't aim to patch/modify user.js by too much. This might be a bit surprising behavior for some of the users but this is what user.js is doing by the default and it is currently outside of the scope for this PKGBUILD to change that. However unlike to user.js you can use about:config to override these settings, as policy utilizes the defaultPref() function to set these. It also doesn't have to be cleaned up.

Most gecko-based browsers should be installed in /usr/lib on Arch by default but on AUR there are a few exceptions like waterfox-g*-bin packages, for which this script will install policy in /opt instead. You are free to set your own list of browsers by editing this PKGBUILD.

I meant that all these *-arkenfox-autoconfig packages should install LICENSE-arkenfox-v$pkgver.txt file in their respective /usr/share/licenses/$pkgname.

I don't really like the idea of duplicate files on FS, symlinks are kinda thing for doing so. Again, I'm not even sure IF I should define that there's a license, given those packages installed by themselves (excluding all dependencies) don't really provide anything, other than a broken symlink at this point.

Legally speaking, I don't even need to. There's a great rationale why to distribute each MIT license individually for each software, but none about distributing the multiple instances of the exactly the same license file for the same file.

At this point, I'd just rather make license in my subpackages point to something like None or Unlicense, given... well.. there's nothing to license in them other than symlink pointing to the file in another package. Symlinks by themselves don't provide any licensed material or data associated to linked file.

I meant that all these *-arkenfox-autoconfig packages should install LICENSE-arkenfox-v$pkgver.txt file in their respective /usr/share/licenses/$pkgname

@micwoj92 It should already be installed.

I don't see any reason why my sub-packages should provide any other license, I might rather update their metadata, to remove license field altogether; although I might make sure first if there's any stance at what should be made for the packages like mine since I haven't met much packages like mine, given they only provide symlinks on the filesystem for the appropriate Firefox browsers.

From the licensing point of view, everything should be fulfilled when it is provided like that. Upstream project is attributed correctly (2 paragraphs of MIT license), as the license is distributed alongside the packages. It's more of the metadata thing, whenever I should also inform about the license in subpackages or not.

Please install license file for all packages.

@turbulent Checking this right now, I don't see a reason ETP wouldn't be set, at least unless you didn't disable it voluntarily (this package does not replace user configuration, it is supposed to replace Firefox defaults only).

I need more info to actually guess what's wrong, if anything, on my side. On my Arch setup, this package just works fine. At least once I've updated it recently to the latest version.

@turbulent Thanks for side notes, I didn't noticed the conversation there, I'll actually check the config it produces and update the app itself afterwards. You might as well check yourself if the config produced by the script distributed via gists functions all-right as well by running it on the current build of the user.js. It should also be explained this package does not tinker with the user.js defaults, and those actually began to become more relaxed than before for some cases.

I use it myself so if some policy isn't actually applied where it should be, sure thing I want to fix it 🙂. Right now unfortunately I'm not around my PC, so I might take before I take any action on that package.

It doesn't set ETP to strict for me.

@MarsSeed

unmaintained and broken fork

It will still be maintained for some time and don't know what you mean by broken. If you have other issues than package name, then you can report that me.

@MarsSeed, I currently see the same maintainer for both waterfox-bin and waterfox-g-kpe and given waterfox-g-kpe seems to be quite advertised here I would believe this package not to be that much unmainained. I think I'll probably stay at waterfox-g since waterfox-bin already provides it and I'm unsure whenever waterfox-g-kpe is going to provide this as well. Also this package is currently incompatible with the watefox, since it seems to install itself to /usr/lib, so I feel more safe using waterfox-g right now than waterfox. Also, I'll probably intentionally not bump the pkgrel, since there should be no changes done to the build script other than subpackage removal.

Please kindly remove the subpackages for waterfox-current and waterfox-g, and in their place, add a new subpackage targeting 'waterfox'.

Upstream's name is WaterFox. To reflect that, the former waterfox-current-bin and waterfox-g-bin AUR packages have both been migrated/renamed to the new waterfox-bin pkg, which provides 'waterfox'.

(And waterfox-g-kpe is an unmaintained and broken fork, which will need to get their patches and build updated, and its name and provides field changed - or else it might be deemed obsolete and get deleted.)

Thank you for maintaining this package.