Get Gentoo!
gentoo.org sites
gentoo.org Wiki Bugs Forums Packages
Planet Archives Sources
Infra Status
summaryrefslogtreecommitdiff
path: root/www-client/chromium
Commit message (Collapse)AuthorAgeFilesLines
* www-client/chromium: do a better job of forcing ClangMatt Jolly2 days4-36/+32
| | | | | | | | | | | | | | | | | | | | When enabling the Rust eclass, we started directly using `llvm-r1_pkg_setup`, assuming that this combination would be sufficicent, however due to forcing `CC` (etc) to variations on `${CHOST}-clang" _before_ calling `llvm-r1_pkg_setup`, these would always be forced to the newest version in `PATH` instead of the one matching `LLVM_SLOT` due to the eclass fixing the version before doing any `PATH` manipulation. To ensure a consistent build environment, we will: 1. Explicitly include `-${LLVM_SLOT}` in `CC`, `CPP`, `CXX` 2. Set these variables (and `AR` and `NM`) after `llvm-r1_pkg_setup` has done its PATH manipulation. Bug: https://bugs.gentoo.org/935689 Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: drop 132.0.6834.6Matt Jolly2 days2-1436/+0
| | | | Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: drop versionsMatt Jolly2 days4-4211/+0
| | | | Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: Stabilize 131.0.6778.85 arm64, #944073Sam James9 days1-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* www-client/chromium: Stabilize 131.0.6778.85 amd64, #944073Sam James9 days1-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* www-client/chromium: drop 133.0.6835.3Matt Jolly10 days2-1455/+0
| | | | Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: add 133.0.6847.2Matt Jolly10 days2-0/+1464
| | | | Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: add 132.0.6834.15Matt Jolly11 days2-0/+1436
| | | | Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: add 131.0.6778.85Matt Jolly12 days2-0/+1425
| | | | | Bug: https://bugs.gentoo.org/944072 Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: update ppc64 handling in 133Matt Jolly2024-11-172-13/+32
| | | | | | | | | | - Use Solid Silicon patches - Get patch order from sources - Add missing debian rust patch to chromium-tarballs (from Raptor patchset) Bug: https://bugs.gentoo.org/940304 Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: add 133.0.6835.3, drop 132.0.6821.2Matt Jolly2024-11-172-6/+10
| | | | Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: add 131.0.6778.69, 132.0.6834.6Matt Jolly2024-11-163-0/+2861
| | | | | Bug: https://bugs.gentoo.org/943403 Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: set RUST_NEEDS_LLVMSam James2024-11-152-0/+2
| | | | | | | This was set in 129, 130 but not 131 or 132. Closes: https://bugs.gentoo.org/943495 Signed-off-by: Sam James <sam@gentoo.org>
* www-client/chromium: drop 130.0.6723.91-r1, 131.0.6778.24-r1Matt Jolly2024-11-133-2784/+0
| | | | Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: drop 131.0.6753.0-r1Matt Jolly2024-11-132-1396/+0
| | | | Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: add 132.0.6821.2Matt Jolly2024-11-133-0/+1537
| | | | Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: restrict LLVM_COMPATMatt Jolly2024-11-112-2/+2
| | | | | | | | The combination of RUST_MIN_USE and LLVM_COMPAT means that llvm_slot_17 will never be able to generate an appropriate dependency. Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: add missing test exclusionsMatt Jolly2024-11-111-0/+27
| | | | | | | | | These were dropped during the great rust upheaval of 2024. More seriously, the -r1 revbump was made before they were added and the change was not noticed. Restored from git history. Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: add 131.0.6778.33Matt Jolly2024-11-112-0/+1424
| | | | | | | Trying something new: 131 has hit early stable. We will promote it to the stable subslot but not file a stablereq. Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: fix src_unpackMatt Jolly2024-11-091-2/+2
| | | | | | | | | | | | To avoid Gentoo-generated tarballs colliding with (e.g.) downstream tarballs of ungoogled-chromium we rename the Gentoo tarballs. Unfortunately the corresponding change to src_unpack did not make it into the ebuild as published. Closes: https://bugs.gentoo.org/943115 Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: Update LLVM_COMPAT to 18Matt Jolly2024-11-091-1/+1
| | | | | | | | | | | | While Chromium is strictly buildable with LLVM 17, our RUST_MIN_VER results in all Rust impls that support LLVM 17 being filtered out. Update RUST_COMPAT so that the package can be built. Signed-off-by: Matt Jolly <kangie@gentoo.org> Signed-off-by: Matt Jolly <kangie@gentoo.org>
* */*: update for slotted RustMatt Jolly2024-11-095-666/+80
| | | | | | | | | | | | | | Tidyups: - $(cargo_crate_uris) - Rust BDEPENDS come from the eclass except in very rare circumstances (RUST_OPTIONAL=1) - RUST_M{AX,IN}_VER where required. - Suboptimal crate separator (`-` -> `@`) Signed-off-by: Matt Jolly <kangie@gentoo.org> Closes: https://github.com/gentoo/gentoo/pull/39218 Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: add 130.0.6723.116Matt Jolly2024-11-062-0/+1525
| | | | | Bug: https://bugs.gentoo.org/942924 Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: fix duplicate KEYWORDS and revert #942590 stabilizationEli Schwartz2024-11-042-6/+2
| | | | | | | | | | | | | | | Having double KEYWORDS= in an ebuild makes tooling such as ekeyword barf and violates https://projects.gentoo.org/qa/policy-guide/ebuild-format.html#pg0105 Instead, we negate the comparison and simply define KEYWORDS= only when it should have meaningful values. The stabilization needs to be rolled back as it fails checks once actually applied -- due to ffmpeg-chromium. Bug: https://bugs.gentoo.org/942590 Signed-off-by: Eli Schwartz <eschwartz@gentoo.org>
* www-client/chromium: Stabilize 130.0.6723.91 arm64, #942590Sam James2024-11-051-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* www-client/chromium: Stabilize 130.0.6723.91 amd64, #942590Sam James2024-11-051-1/+1
| | | | Signed-off-by: Sam James <sam@gentoo.org>
* www-client/chromium: drop 128.0.6613.137Matt Jolly2024-11-022-1457/+0
| | | | | | | | Old, vulnerable. Only kept around for ppc64 and broken even there. Bug: https://bugs.gentoo.org/940304 Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: keyword 130.0.6723.91 for ~ppc64Matt Jolly2024-11-022-19/+36
| | | | | | | | | | | | | | Move source for ppc64le patchset from raptor engineering to openPOWER. Drop our ppc64le tarball (which has dwindled over time) in favour of conditional application of patches from our chromium-patches tarball, something that was probably long overdue. Bug: https://bugs.gentoo.org/940304 Reported-by: zin0 <z_i_n_o@bluewin.ch> Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: update SRC_URIMatt Jolly2024-11-013-8/+7
| | | | | | | | | | Infra have graciously provided a CDN for these tarballs. Update the chromium-testfonts tarball to use the first 10 digits of the SHA256 hash in its rename; it seems to be portable between major versions. Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: add 131.0.6778.24Matt Jolly2024-11-012-0/+1511
| | | | Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: drop 130.0.6723.58, 130.0.6723.69Matt Jolly2024-11-013-3129/+0
| | | | Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: add 130.0.6723.91Matt Jolly2024-10-312-0/+1484
| | | | | Bug: https://bugs.gentoo.org/942503 Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: add 130.0.6723.69Matt Jolly2024-10-292-0/+1563
| | | | Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: Stabilize 130.0.6723.58 arm64, #941720Arthur Zamarin2024-10-241-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* www-client/chromium: Stabilize 130.0.6723.58 amd64, #941720Arthur Zamarin2024-10-241-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* www-client/chromium: drop 130.0.6723.44Matt Jolly2024-10-182-1499/+0
| | | | Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: add 130.0.6723.58Matt Jolly2024-10-182-0/+1566
| | | | | Bug: https://bugs.gentoo.org/941600 Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: remove unused patchMichael Mair-Keimberger2024-10-151-57/+0
| | | | | Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at> Signed-off-by: Conrad Kostecki <conikost@gentoo.org>
* www-client/chromium: drop 130.0.6723.31Matt Jolly2024-10-132-1466/+0
| | | | Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: drop 129.0.6668.70, 129.0.6668.89Matt Jolly2024-10-133-2928/+0
| | | | Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: Enable Control-flow Integrity (CFI)Matt Jolly2024-10-132-12/+11
| | | | | | | | | | | | | | | | | | | | | This relies on Clang's CFI mechanisms, and is dependent on split LTO Units, which require a "nightly" Rust, years after the feature's implementation, with it being in widespread use in the real world for software packaged on stable systems. Because there is no better way to go about this we are forced to YOLO it and set `RUSTC_BOOTSTRAP=1` in the ebuild. Google's default build uses a nightly compiler, so this should not cause any issues. CFI will be enabled on a platform if LTO is enabled, unless this needs to be filtered for non x86_64 systems. According to Google this should result in a slight (<1%) overhead in terms of CPU and a small increase (<10%) to the size of the compiled binary. Memory overhead is minimal. Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: add 131.0.6753.0Matt Jolly2024-10-125-0/+1610
| | | | | | | | | | | | | | | | | This commit brings the development channel into ::gentoo. We may remove it if the overheads prove too much, and it is not a priority for updates. The hope is that the development slot, if kept up-to-date, will provide additional time to adapt the ebuild to upcoming major versions of Chromium before they hit stable and become security issues. Changes: - use `filter-lto` and rely on GN to appropriately set LTO options. - Remove `updater` force-disable - it shouldn't be enabled anyway. Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: add 130.0.6723.44Matt Jolly2024-10-122-0/+1498
| | | | Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: Stabilize 129.0.6668.89 arm64, #940677Arthur Zamarin2024-10-101-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* www-client/chromium: Stabilize 129.0.6668.100 amd64, #941213Arthur Zamarin2024-10-101-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* www-client/chromium: Stabilize 129.0.6668.100 arm64, #941213Arthur Zamarin2024-10-101-1/+1
| | | | Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
* www-client/chromium: make rust profiler sanity check more reliableMatt Jolly2024-10-102-12/+14
| | | | | | | | | | | | | | On ppc64le the machine hardware name printed out by 'uname -m' is 'ppc64le' but the rust target is called 'powerpc64le'. As a result, the build process will always die even if we're using a rust compiler built with USE='profiler'. Use this opportunity to tighten up some language in the ebuild and elaborate more in comments. Closes: https://bugs.gentoo.org/940729 Co-authored-by: zin0 <z_i_n_o@bluewin.ch> Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: add 129.0.6668.100Matt Jolly2024-10-102-0/+1464
| | | | | Bug: https://bugs.gentoo.org/941186 Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: drop 129.0.6668.58, 130.0.6723.19Matt Jolly2024-10-053-2915/+0
| | | | Signed-off-by: Matt Jolly <kangie@gentoo.org>
* www-client/chromium: add 130.0.6723.31Matt Jolly2024-10-052-0/+1465
| | | | Signed-off-by: Matt Jolly <kangie@gentoo.org>