- #UNGOOGLED CHROMIUM BINARY INSTALL#
- #UNGOOGLED CHROMIUM BINARY ARCHIVE#
- #UNGOOGLED CHROMIUM BINARY CODE#
# if it exists, remove the old void-packages/srcpkgs/ungoogled-chromium folder
#UNGOOGLED CHROMIUM BINARY ARCHIVE#
Recommended to use git clone -depth 1 to fetch only the current branch instead of the full tree.Ĭlone this repository or download the source archive from the Releases page.
#UNGOOGLED CHROMIUM BINARY INSTALL#
Relevant section: Quick startĬlone the void-packages git repository and install the bootstrap packages: $ git clone git:///void-linux/void-packages.git If you haven't set up the void-packages repository consult this page for more information. Testing changes python3 -m pip install -r utilities/requirements.Ungoogled Chromium template and builds for Void Linux, based on the void-packages Chromium template. # In GitHub, create a pull request in ungoogled-software/ungoogled-chromium-binaries with the new change in YOURNAME/ungoogled-chromium-binaries Ensure commits are correct before proceeding # A commit will be created automatically. utilities/submit_github_binary.py -git path/to/ungoogled-chromium-debian -username YOURNAME -output config/platforms/debian/buster_amd64/ ~/ungoogled-chromium/build/ungoogled-chromium* # NOTE: You can use either -git to fetch the latest tag on the current branch, or specify it manually with -tag # Create the directories debian/ and debian/buster_amd64 with corresponding display_name files in config/platforms/ ONLY if they do NOT exist. Upload all necessary files from /home/user/ungoogled-chromium/buildspace/ into the Release.Ĭd ungoogled-chromium-binaries # The same as the one setup above 567-1: # In GitHub, create a new Release on YOURNAME/ungoogled-chromium-binaries with a name ".567-1" (without quotes) and a new tag ".567-1" (without quotes insert it into the tag field). The following example demonstrates publishing Debian 9 (buster) amd64 packages located in /home/user/ungoogled-chromium/build/ (which is assumed to be the shell expanded form of ~/ungoogled-chromium/build/) for ungoogled-chromium version. Replace YOURNAME in the steps with your GitHub username.įirst-time setup: # In GitHub, fork ungoogled-software/ungoogled-chromium-binaries to YOURNAME/ungoogled-chromium-binaries Additional changes can be made to the website configuration before step 5 as necessary.Įxample command-line steps (with comments, denoted by a hash # symbol).If binaries are uploaded elsewhere, then the INI must be created by other means. submit_github_binary.py is currently restricted to generating INI files with URLs to binaries in GitHub releases.This can be bypassed if one is part of the Binaries Team.Make a pull request against the main repository. Push your changes in the repository these changes should only be of files in config/.If a directory structure in config/platforms doesn't exist for the binary's target platform and version, create the necessary directories with the associated display_name files in the same manner as existing platforms.Use the -h or -help argument for more details. It requires paths to a locally stored copy of the binaries for computing hashes. Use utilities/submit_github_binary.py to generate an INI file with the correct URLs to the GitHub Release.The tag name used must be unique for each Release it normally matches the ungoogled-chromium version. using GitHub's Release feature) in the fork and upload binaries to it. If this has been done before, pull in new changes from this one if necessary.Fork the main binaries repository ( ungoogled-software/ungoogled-chromium-binaries).
#UNGOOGLED CHROMIUM BINARY CODE#
Ensure your binary has source code published to a platform repo.An example of these steps is in the next section. Python 3 for all scripts under utilities/.Publishing new binariesĮnsure your binary has source code published to a platform repo. If you have questions or suggestions, please create an Issue. When creating new pages or adding new versions, use an existing version as a template to follow. This website uses GitHub Pages on the master branch.įor problems, suggestions, and questions, please use the Issue tracker. Because these binaries are not necessarily reproducible, authenticity cannot be guaranteed. IMPORTANT: These binaries are provided by anyone who are willing to build and submit them. Website for ungoogled-chromium contributor-submitted binaries (contributor binaries).
0 kommentar(er)
