mirror of
https://github.com/chromebrew/chromebrew.git
synced 2026-05-01 03:00:26 -04:00
* Rebuild gettext with upstream patch. Signed-off-by: Satadru Pramanik <satadru@gmail.com> * Abort build before upload if crew check fails. Signed-off-by: Satadru Pramanik <satadru@gmail.com> * Sanitize download filename in downloader and ConvenienceFunctions.patch. Signed-off-by: Satadru Pramanik <satadru@gmail.com> * Do not use gitweb.git.savannah.gnu.org url. Signed-off-by: Satadru Pramanik <satadru@gmail.com> * Revert to older working patch. Signed-off-by: Satadru Pramanik <satadru@gmail.com> * Restore usage of downloaded archive.dir. Signed-off-by: Satadru Pramanik <satadru@gmail.com> * Mark packages from successful builds as automatically buildable. * gettext_rebuild: Package File Update Run on linux/386 container. * gettext_rebuild: Package File Update Run on linux/amd64 container. * gettext_rebuild: Package File Update Run on linux/arm/v7 container. --------- Signed-off-by: Satadru Pramanik <satadru@gmail.com> Co-authored-by: Satadru Pramanik <satadru@gmail.com> Co-authored-by: satmandu <satmandu@users.noreply.github.com> Co-authored-by: chromebrew-actions[bot] <220035932+chromebrew-actions[bot]@users.noreply.github.com> Co-authored-by: chromebrew-actions[bot] <chromebrew-actions[bot]@users.noreply.github.com>
Tools
This directory contains a number of tools used to assist in the development of Chromebrew.
Check for packages needing updates
These are a collection of scripts and files used to detect if packages need an update. Coverage is spotty, and the majority of packages are unsuppported.
check.rbcheck_updates.shcompare_packages.shcore_packages.txtpackages.yaml
Add missing dependencies to packages
This script adds missing dependencies to packages by checking their library dependencies and what crew package provides them.
getrealdeps.sh
Upload package binaries to GitLab
This script uploads built packages to GitLab, where we currently host precompiled binaries.
gl.sh
Valid licenses for packages
This file contains guidance on formatting conventions for what to put in the license field of packages. There is also a rough list of what licenses are used, although this is incomplete and a little outdated.
licenses.txt