From 1749bce3917e81c4c38b33f52f1e0e9c6d7812bd Mon Sep 17 00:00:00 2001 From: Bert van der Weerd Date: Wed, 4 May 2022 13:39:18 +0200 Subject: [PATCH] Updated README.md --- README.md | 19 +++++++++++-------- README.md.in | 2 +- 2 files changed, 12 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index 845acea..6688b26 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ List of browser build sub projects. These are the locations where people have th Currently active build repositories: * [Arch](https://gitlab.com/librewolf-community/browser/arch): Arch Linux -* [Bsys5](https://gitlab.com/librewolf-community/browser/bsys5): deb/rpm for Mint,Fedora,Ubuntu; dmg for MacOS. +* [Bsys5](https://gitlab.com/librewolf-community/browser/bsys5): .deb/.rpm for Mint, Fedora, Ubuntu; .dmg for MacOS. * [Debian](https://gitlab.com/librewolf-community/browser/debian): bgstack15 version * [Fedora](https://gitlab.com/librewolf-community/browser/fedora): bgstack15 version * [Flatpak](https://gitlab.com/librewolf-community/browser/flatpak): Flatpak @@ -24,11 +24,11 @@ Currently active forks: ## LibreWolf build instructions -There currently are two ways to build LibreWolf. You can either use the source tarball or compile directly with this repository. +There are two ways to build LibreWolf. You can either use the source tarball or compile directly with this repository. ### Building from the Tarball -First, let's **[download the latest tarball](https://gitlab.com/librewolf-community/browser/source/-/jobs/artifacts/main/raw/librewolf-100.0-1.source.tar.gz?job=Build)**. This tarball is the latest produced by the [CI](https://gitlab.com/librewolf-community/browser/source/-/jobs). You can also check the sha256sum of the tarball there. +First, let's **[download the latest tarball](https://gitlab.com/librewolf-community/browser/source/-/jobs/artifacts/main/raw/librewolf-99.0.1-4.source.tar.gz?job=Build)**. This tarball is the latest produced by the [CI](https://gitlab.com/librewolf-community/browser/source/-/jobs). You can also check the sha256sum of the tarball there. ``` tar xf @@ -107,8 +107,7 @@ Now change the source tree the way you want, keeping in mind to `git add` new fi cd firefox- git diff 4b825dc642cb6eb9a060e54bf8d69288fbee4904 HEAD > ../my-patch-name.patch ``` -This ID is the hash value of the first commit, which is called `initial`. dont forget to commit -changes before doing this diff, or the patch will be incomplete. +This ID is the hash value of the first commit, which is called `initial`. Dont forget to commit changes before doing this diff, or the patch will be incomplete. ### How to create a patch for problems in Mozilla's [Bugzilla](https://bugzilla.mozilla.org/). @@ -146,9 +145,13 @@ hg diff > ../my-nightly-patch.patch ``` And it can be uploaded to Bugzilla. -##### *(copy of Mozilla readme)* Now the fun starts +##### *(excerpt from the Mozilla readme)* Now the fun starts Time to start hacking! You should join us on [Matrix](https://chat.mozilla.org/), say hello in the [Introduction channel](https://chat.mozilla.org/#/room/#introduction:mozilla.org), and [find a bug to start working on](https://codetribute.mozilla.org/). See the [Firefox Contributors’ Quick Reference](https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html#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](https://firefox-source-docs.mozilla.org/setup/macos_build.html), [Windows](https://firefox-source-docs.mozilla.org/setup/windows_build.html). 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. +## Hey, I'm using MacOS 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](https://firefox-source-docs.mozilla.org/setup/macos_build.html): The cross-compiled Mac .dmg files are somewhat new. They should work, perhaps with the exception of the `make setup-wasi` step. +* [Windows](https://firefox-source-docs.mozilla.org/setup/windows_build.html): Building on Windows is not very well tested. + +Help with testing these targets is always welcome. \ No newline at end of file diff --git a/README.md.in b/README.md.in index 1ab5f55..6688b26 100644 --- a/README.md.in +++ b/README.md.in @@ -107,7 +107,7 @@ Now change the source tree the way you want, keeping in mind to `git add` new fi cd firefox- git diff 4b825dc642cb6eb9a060e54bf8d69288fbee4904 HEAD > ../my-patch-name.patch ``` -This ID is the standard ID of any empty git repository. You can now also delete the temporary firefox souce tree. +This ID is the hash value of the first commit, which is called `initial`. Dont forget to commit changes before doing this diff, or the patch will be incomplete. ### How to create a patch for problems in Mozilla's [Bugzilla](https://bugzilla.mozilla.org/).