projects/aports·tree master · refs

Files

ModeNameSize
040000../--
1006440001-hotfix-ignore-a-new-warning-in-rust-1.89.patch882 B
100644APKBUILD22.4 KiB
100644README.md2.8 KiB
100644compiler.patch8.4 KiB
100644default.conf373 B
100644disable-dns_config_service.patch678 B
100644disable-failing-tests.patch536 B
100644electron-launcher.sh764 B
100644electron.desktop151 B
100644electron_chrome-test-no-depend-test_data-cipd.patch535 B
100644electron_do-not-build-environ-linux.patch390 B
100644electron_do-not-strip-binaries.patch4.2 KiB
100644electron_fix-yarn412-lockfile.patch2.0 KiB
100644electron_icon.patch599 B
100644electron_pin-keys-4-5-4.patch3.3 KiB
100644electron_python-jinja-3.10.patch815 B
100644electron_shell-file-dialog-drop-glibc.patch449 B
100644electron_system-zlib-headers.patch317 B
100644electron_unbundle-node.patch4.6 KiB
100644electron_use-system-yarn.patch461 B
100644electron_webpack-hash.patch349 B
100644fc-cache-version.patch481 B
100644fix-ffmpeg-codec-list.patch586 B
100644fstatat-32bit.patch695 B
100644gdbinit.patch616 B
100644generic-sensor-include.patch372 B
100644headless-shell-no-license.patch708 B
100644musl-sandbox.patch5.0 KiB
100644musl-tid-caching.patch2.1 KiB
100644net-test-no-vpython.patch819 B
100644net-test-pyws3-py3.12.patch1.9 KiB
100644no-execinfo.patch2.2 KiB
100644no-mallinfo.patch4.6 KiB
100644no-res-ninit-nclose.patch1.0 KiB
100644no-sandbox-settls.patch631 B
100644partalloc-no-tagging-arm64.patch1.1 KiB
100644pvalloc.patch1.4 KiB
100644rust-cbor.patch1.5 KiB
100644temp-failure-retry.patch713 B

testing/electron/README.md

electron

This is the electron package for Alpine Linux.

Please report any issues using Gitlab and tag @ayakael

Building electron

Electron is an application framework based on chromium. Just like chromium, and any Google application, the build process is a form of [hostile architecture] (https://en.wikipedia.org/wiki/Hostile_architecture) It’s quite literally chromium with patches applied on top for the most part. The build process applies a series of git patches against chromium from directories with a script.

Its source code isn’t available as a downloadable tarball. It is only fetchable using Google’s gclient available in depot_tools with a reimplemented version in the teapot package. By executing, abuild snapshot, the tarball can be fetched and packaged, as long as gclient is in your path. For ease of maintenance, a workflow on Ayakael’s Forge automatically fetches and packages the source code on new releases and makes it available in a generic Forgejo repository.

Electron maintenance cycle

Security / bug fixes land from upstream land randomly, but chromium security fixes land basically weekly around Tuesday in America/Los_Angeles. Minor relases only require an upgrade to the electron packages. It is advisable to follow chromium weekly security fixes, although following electron minor releases is fine.

Major version upgrades require a more thorough approach. For one, most changes can be backported from chromium APKBUILD by diffing the previous version packaged with electron with the current (set with _chromium var). You also need to rebuild all electron apps, with patches sometimes necessary when upstream bumps to a new nodejs major verion. Major electron releases are every two chromium major releases, with [dates known well ahead] (https://chromiumdash.appspot.com/schedule) with a few major releases of electron officially supported at a time.

Steps, in a nutshell:

  1. Set pkgver to up-to-date version

  2. Optional: fetch source-code using abuild snapshot, making sure gclient is in your path

  3. Update source checksum using abuild checksum

  4. If major update, backport changes from chromium aport and bump pkgrel for all electron-based applications.

Why is this package still in testing

Work is under way to make this aport ready for community

Until that happens, this package is also kept-to-date against the latest release of Alpine Linux in Ayakael’s Forge This is true of all Ayakael’s packages still in testing.