#UNGOOGLED CHROMIUM BINARY HOW TO#
#UNGOOGLED CHROMIUM BINARY INSTALL#
#UNGOOGLED CHROMIUM BINARY CODE#
#UNGOOGLED CHROMIUM BINARY PASSWORD#

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. Noextract=('ungoogled-chromium-$pkgver-$pkgrel-x86_64. for ungoogled-chromium contributor-submitted binaries (contributor binaries). '$pkgver-$pkgrel/ungoogled-chromium-$pkgver-$pkgrel-x86_64.' 'kwallet: support for storing passwords in KWallet on Plasma'Ĭonflicts=('ungoogled-chromium' 'chromium')

#UNGOOGLED CHROMIUM BINARY PASSWORD#

': password storage backend on GNOME / Xfce' 'kdialog: support for native dialogs in Plasma' Optdepends=('pipewire: WebRTC desktop sharing under Wayland' Pkgdesc='A lightweight approach to removing Google web service dependency (binary release)'ĭepends=('gtk3' 'nss' 'alsa-lib' 'xdg-utils' 'libxss' 'libcups' 'libgcrypt' 'ttf-liberation' 'systemd' 'dbus' 'libpulse' 'pciutils' 'libva' 'desktop-file-utils' 'hicolor-icon-theme'

#UNGOOGLED CHROMIUM BINARY HOW TO#

There are 2 tarballs there, is that the reason yay or pamac has no clue on how to proceed?Ĭontents of PKGBUILD # Maintainer: KuoHuanHuan I am a bit lost here, how should I proceed? Should yay just have picked this up on itself? So having an aur helper doesn’t make a difference in my case. When installing this package with yay, it seems all it does is creating these files in ~/.cache/yay and then nothing. So I figured I might need an aur helper like yay to pick this up. Installing it with pamac results in just downloading and then nothing. There is a binary package on aur ungoogled-chromium-binary.

#UNGOOGLED CHROMIUM BINARY INSTALL#

I am trying to install ungoogled-chromium.

Ungoogled chromium binary