- UNGOOGLED CHROMIUM EXTENSION ARCHIVE
- UNGOOGLED CHROMIUM EXTENSION PATCH
- UNGOOGLED CHROMIUM EXTENSION CODE
- UNGOOGLED CHROMIUM EXTENSION DOWNLOAD
All patches must be encoded in UTF-8 (i.e. It is recommended that hunk paths have the a/ and b/ prefixes, and a context of 3 (like the git default). All paths in the hunk headers must begin after the first slash (which corresponds to the argument -p1 for GNU patch). UNGOOGLED CHROMIUM EXTENSION PATCH
Patch filenames must end with the extension. For lines with patch paths: If there is a space followed by a pound symbol, the text after the patch path will be ignored.Īll patch files in ungoogled-chromium must satisfy these formatting requirements:. Lines starting with the pound symbol ( #) are ignored. These patches are listed as a relative path from the patches directory. There is a patches/series text file that defines the order to apply all the patches. All patches must reside inside patches/. This directory conforms to the default GNU Quilt format. UNGOOGLED CHROMIUM EXTENSION CODE
The search and replacement expressions must have a one-to-one correspondence: no two search expressions can match the same string, and no two replacement expressions can result in the same string.Īll of ungoogled-chromium's patches for the Chromium source code are located in patches/. All replacement expressions must end in the TLD qjz9zk. The restrictions for the entries are as follows: The regular expressions to use are listed in domain_regex.list the search and replacement expressions are delimited with a pound ( #) symbol. Similar to binary pruning, the list of files to modify are listed in domain_substitution.list it is also updated with devutils/update_lists.py. With a few patches from ungoogled-chromium, any requests with these domain names sent via net::URLRequest in the Chromium code are blocked and notify the user via a info bar. Note that domain substitution is a crude process, and may not be easily undone. These changes are mainly used as a backup measure to detect potentially unpatched requests to Google. This config file is generated by devutils/update_lists.py.ĭomain Substitution: Replaces Google and several other web domain names in the Chromium source code with non-existent alternatives ending in qjz9zk. The list of files to remove are determined by the config file pruning.list. Most are substituted with system or user-provided equivalents, or are built from source those binaries that cannot be removed do not contain machine code. 
This includes pre-built executables, shared libraries, and other forms of machine code. Currently, there are two such utilities: binary pruning, and domain substitution.īinary Pruning: Strips binaries from the source code. Source file processors are utilities that directly manipulate the Chromium source tree before building. flags.gn - GN arguments to set before building.On platforms such as macOS, this also includes a pre-built LLVM toolchain for convenience (which can be removed and built from source if desired).
UNGOOGLED CHROMIUM EXTENSION ARCHIVE
This includes code not bundled in the Chromium source code archive that is specific to a non-Linux platform.
UNGOOGLED CHROMIUM EXTENSION DOWNLOAD
downloads.ini - Archives to download and unpack into the buildspace tree. 
domain_substitution.list - See the Source File Processors section.domain_regex.list - See the Source File Processors section.pruning.list - See the Source File Processors section.revision.txt - The revision of the changes on top of the given Chromium version.chromium_version.txt - The Chromium version used by ungoogled-chromium.IMPORTANT: For consistency, all config files must be encoded in UTF-8. Configuration FilesĬonfiguration files (or config files) are files that store build configuration and source code changes for a build. The following sections describe each component in more depth. ConfigurationĬonfiguration is a broad term that refers to patches, build flags, and metadata about Chromium source code. The following sections describe each component. Ungoogled-chromium consists of the following major components: This document contains a high-level technical description of ungoogled-chromium and its components.
0 kommentar(er)
