I couldn't find any code for langpacks in the repos.
#Librewolf sync for free#
Like disabled Sync or most of WebRTC that might be useful for free software like Jitsi. Default preferences might put off some users, as sometimes they might seem too strict.I guess it's necessary to try to communicate and sort this out with LibreWolf project first. It's not clear if project understanding of software freedom concepts aligns with FSDG and Parabola standards.Hopefully less effort for updating the package, since most of rebranding and deactivating of unwanted functionality is handled upstream.Release delays after a few recent official Firefox releases have been no more than a few days."Recommendations" from (AMO) for extensions and themes.some functionality is disabled via either preference overriding or built-in Enterprise Policies, for example:.most of the URLs to Mozilla domains removed via preference overriding mechanism, similarly to what Parabola does in vendor.js.Examples of the changes that are already applied upstream:.GMP (I guess applies here too), telemetry-, health-, crash-, other-reporting implementations that are currently just disabled via preferences / policies.DRM implementation (please see note for details).recommendations of nonfree software like Firefox Developer Edition.Examples of these changes include removing the following: To comply with FSDG and Parabola standards, it's necessary to either convince upstream to make some changes, or to do them downstream.are welcome, because as usual, the following may not be correct. Please refer to the project website, docs, and code first.Īny constructive corrections, comments, concerns, criticism, etc.
Validating json + multiline parsing.I've built librewolf 75.0-1 locally after adding only the following 3 lines to the PKGBUILD from the AUR: The only scenario I can imagine that there is policy being set by librewolf #Implementing some sort value changer for policiesĬurrently the policies.json can only comment out keys, not change a value. I am mostly responsive on mail don't hesitate to ask, send PR or issue to me. However, any function call pref() from a /usr/lib/librewolf/browser/defaults/preferences/*.jsĭoes behave more or less like "defaultPref" instead, so user changes done via GUI will be kept on restart.Īlso lockPref, lock_pref, defaultPref, default_pref are not working function calls in /usr/lib/librewolf/browser/defaults/preferences/*.js so they have no effect but does work at $HOME/.librewolf/user-profile/user.js. it shows up in about:config as "user set". If you set a particular preference this way, Librewolf.cfg states // "pref" : Sets the preference as if a user had set it, every time you start the browser. #Caveats and what to take pay more attention Is redundant, however that might change in future. Note - currently there is no backup() in the PKGBUILD of librewolf so uncomment-hook It's there to basically return the librewolf.cfg and policies.jsonīack to stock to prevent any *.pacnew files from being created by deault. Undo every modification from first hook prior the Librewolf update. The second hook /usr/share/libalpm/hooks/librewolf-cfg-uncomment-out.hook will
#Librewolf sync install#
Will be applied post install of this package and post upgrade of Librewolf itself. The first hook /usr/share/libalpm/hooks/librewolf-cfg-comment-out.hook Many setting from librewolf.cfg and policies.json cannot bet set via *.jsįile at $HOME/.librewolf or at /usr/lib/librewolfīasically this package will put 2 pacman hooks into the ALPM directories. Put your created files here $ ls /usr/lib/librewolf/browser/defaults/preferencesĬtrl-q-disable.js urlbar-suggestions.js wayland.jsĪny values blocked by librewolf.cfg and policies.json can be unblocked You should do create a new files with your custom prefs yourself. This package will allow you to undo the hardoced values. If there is a entry blocking you in any way, This hook package will allow you to unblock defaults that are blockedīy librewolf.cfg and policies.json post install.
0 kommentar(er)
