0
Fork 0
mirror of https://codeberg.org/librewolf/source.git synced 2024-12-22 05:33:03 -05:00
LibreWolf - Source Archive
Find a file
Bert van der Weerd 408c041ae0 Merge branch 'main' into 'main'
Add new LibreWolf fork

See merge request librewolf-community/browser/source!22
2022-03-14 20:19:52 +00:00
assets Merge branch 'hide_history_dropdown' into 'main' 2022-03-09 11:34:01 +00:00
patches update unity and kde integration patches for 98.0 2022-03-10 13:38:49 +01:00
scripts include release number in tarball name and improve target names 2022-02-05 16:13:32 +01:00
submodules Release v98.0 2022-03-09 16:17:10 +01:00
themes/browser better icon on macos 2022-02-08 11:40:28 +01:00
.gitignore inbetween commits 2022-01-08 22:55:25 +01:00
.gitlab-ci.yml fix typo 2022-02-07 13:35:18 +01:00
.gitmodules removed pref-pane submodule 2022-02-03 10:17:35 +01:00
LICENSE Add LICENSE 2021-11-19 17:42:30 +00:00
Makefile polish 2022-02-09 13:04:18 +01:00
README.md add new LibreWolf fork 2022-03-13 17:22:37 +04:00
README.md.in add new LibreWolf fork 2022-03-13 17:22:37 +04:00
release v97.0.2 2022-03-05 15:43:41 +01:00
version v98.0 2022-03-09 06:09:51 +01:00

Active repositories and projects

List of browser build sub projects. These are the locations where people have their repositories and build artifacts.

Currently active build repositories:

  • Arch: Arch Linux
  • Bsys5: deb/rpm for Mint,Fedora,Ubuntu; dmg for MacOS.
  • Debian: bgstack15 version
  • Fedora: bgstack15 version
  • Flatpak: Flatpak
  • Gentoo: Gentoo
  • Linux: Flatpak, AppImage, Arch and other Linux builds of the LibreWolf browser.
  • MacOS: The macOS build of LibreWolf.
  • OpenBSD: OpenBSD page
  • Windows: LibreWolf builds for Windows.

Currently active forks:

LibreWolf build instructions

First, let's download the latest tarball. This tarball is the latest produced by the CI. You can also check the sha256sum of the tarball there.

So here is how build LibreWolf for Linux:

tar xf <tarball>
cd <folder>
make setup-wasi bootstrap build package run

How to make a patch:

The easiest way to make patches is to go to the LibreWolf source folder:

cd librewolf-$(cat version)
git init
git add <path_to_file_you_changed>
git commit -am initial-commit
git diff > ../mypatch.patch

We have Gitter / Matrix rooms, and on the website we have links to the various issue trackers.

Building LibreWolf with git:

  1. Clone the git repository via https:
git clone --recursive https://gitlab.com/librewolf-community/browser/source.git

or ssh:

git clone --recursive git@gitlab.com:librewolf-community/browser/source.git

cd into it, build the LibreWolf tarball, bootstrap the build environment, and finally, perform the build:

cd source
make all
make bootstrap
make build

After that, you can either build a tarball from it, or run it:

make package
make run

How to create a patch for problems in Mozilla's Bugzilla.

Well, first of all:

Now that you have a patch in LibreWolf, that's not enough to upload to Mozilla. See, Mozilla only accepts patches against Nightly. So here is how to do that:

hg clone https://hg.mozilla.org/mozilla-unified
cd mozilla-unified
hg update
MOZBUILD_STATE_PATH=$HOME/.mozbuild ./mach --no-interactive bootstrap --application-choice=browser
./mach build
./mach run

Now you can apply your patch to Nightly:

patch -p1 -i ../mypatch.patch

Now you let Mercurial create the patch:

hg diff > ../my-nightly-patch.patch

And it can be uploaded to Bugzilla.

(copy of Mozilla readme) Now the fun starts

Time to start hacking! You should join us on Matrix, say hello in the Introduction channel, and find a bug to start working on. See the Firefox Contributors Quick Reference to learn how to test your changes, send patches to Mozilla, update your source code locally, and more.

Hey, I'm using a Mac or Windows :(

We understand, life isn't always fair 😺. The same steps as above do apply, you'll just have to walk through the beginning part of the guides for MacOS, Windows. To build on Windows is not very well tested. The cross-compiled Mac .dmg files are also relatively new. It should work, perhaps with the exception of the make setup-wasi step. Help testing with these targets is always welcome.