diff options
| author | Matt Jolly <kangie@gentoo.org> | 2026-02-13 19:58:22 +1000 |
|---|---|---|
| committer | Matt Jolly <kangie@gentoo.org> | 2026-02-13 21:50:16 +1000 |
| commit | bb2881df2aae446b0d97fab187cc5e262a78d333 (patch) | |
| tree | e7f9a1429a8ee720f14285cc1e3326fcac632980 /dev-python/google-api-python-client/google-api-python-client-2.187.0.ebuild | |
| parent | ae1a3fbad7fffc60a0149ae280049a0ec9055308 (diff) | |
| download | gentoo-bb2881df2aae446b0d97fab187cc5e262a78d333.tar.gz gentoo-bb2881df2aae446b0d97fab187cc5e262a78d333.tar.bz2 gentoo-bb2881df2aae446b0d97fab187cc5e262a78d333.zip | |
www-client/chromium: add 145.0.7632.67
This commit adds a few fixes and enhancements to the ebuild process:
1. We now run a script (`files/bin-finder.py`) to identify ELF files,
then remove them from the source tree in `src_prepare`. This means
that builds shouldn't fail suddenly on another arch because upstream
shipped an amd64 binary.
2. The `generate-support-files.py` script, which wraps some installer
functions to generate desktop files and manpages (etc), without
resorting to messy `sed`s. This is in response to a regression in the
previous M145 ebuild where the inlined version was was not included
and the defective `sed` statements were used instead.
3. We've reverted to the `@rollup/wasm-node` package, which means that
we are downloading a binary to build Chromium, however: it was
previously shipped in the tarball, is wasm-y and relatively portable,
and has proven to be challenging to package system-wide due to
circular deps.
Bug: https://bugs.gentoo.org/969926
Bug: https://bugs.gentoo.org/970003
Signed-off-by: Matt Jolly <kangie@gentoo.org>
Diffstat (limited to 'dev-python/google-api-python-client/google-api-python-client-2.187.0.ebuild')
0 files changed, 0 insertions, 0 deletions