Arch Linux User Repository

is there a reason to not use system electron?

Aside that I'm not pratical with that

Yes, see this I don't think things have changed meanwhile https://lists.archlinux.org/archives/list/aur-requests@lists.archlinux.org/message/ULRU76CEQWVNDISFAFDE52WHM2XQYNHE/

[...] upstream using a custom version of
`electron` which supports DRM, while it is not supported in the Arch
packages.

It is new to me that installing a package remove core packages

I uninstalled it by accident because it was is a dependency of base-devel :D

@FabioLolix: is there a reason to not use system electron? it works for me with only app.asar and app.asar.unpacked/* (copied from the current installation). I’m not sure about compiled extensions.

(https://wiki.archlinux.org/title/Electron_package_guidelines)

According to my understanding this was caused by a system update.

testing this removed my sudo

It is new to me that installing a package remove core packages

which will be added as dependsdency

@Jogsn: testing this removed my sudo, but I can confirm which is needed as a dependency.

base-devel is assumed to be installed when building, but not at runtime.

(https://wiki.archlinux.org/title/PKGBUILD#makedepends)

Hello. I was unable to launch any game due to the "which" package missing. According to my understanding this was caused by a system update. Manually installing the "which" package from the core repo fixed the issue for me. Maybe this package can be added as a dependency?

For reference here the error from heroics log file:

(11:59:24) INFO:    [Backend]:          Launching Ghostwire Tokyo (007ff8f4e30845a687e66aa77eb3e965)
(11:59:24) INFO:    [Backend]:          Checking if wine version exists: Wine - Wine-GE-latest
(11:59:24) ERROR:   [Backend]:          Error: spawn which ENOENT
at Process.ChildProcess._handle.onexit (node:internal/child_process:286:19)
at onErrorNT (node:internal/child_process:484:16)
at processTicksAndRejections (node:internal/process/task_queues:82:21)

@Yamashiro while I get what you mean I don't think it fits the definition of an optional dependency. It's a useful tool, no question, but it doesn't extend the functionality of the heroic itself, but latches onto it with a hack and a manual intervention.

I've created an AUR comet-gog-git package for comet, that enables achievements when using Heroic. You can add it as an optional dependency for Heroic until it's implemented in the client itself.

Hello Achilleus, I have builded fine with devtools before upload and with makepkg after your comment

Please try to build using with devtools https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot using extra-x86_64-build for convenience)

Every now and then I remove the npm cache folder ~/.npm, not sure I can further help you

Package uploaded on SF at the second try https://sourceforge.net/projects/fabiololix-os-archive/files/Packages/, it always fail at first try

It's me again...

$ LC_ALL=C makepkg -sic
==> Making package: heroic-games-launcher 2.12.0-1 (Sun Jan  7 18:56:00 2024)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating HeroicGamesLauncher git repo...
==> Validating source files with sha256sums...
    HeroicGamesLauncher ... Skipped
==> Extracting sources...
  -> Creating working copy of HeroicGamesLauncher git repo...
Reset branch 'makepkg'
==> Removing existing $pkgdir/ directory...
==> Starting build()...
yarn install v1.22.21
[1/5] Validating package.json...
[2/5] Resolving packages...
warning Resolution field "ts-morph@17.0.1" is incompatible with requested version "ts-morph@^13.0.1"
success Already up-to-date.
$ husky install
husky - Git hooks installed
Done in 0.32s.
yarn run v1.22.21
$ vite build && electron-builder --linux tar.xz
vite v3.2.7 building for production...
error Command failed with exit code 139.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
==> ERROR: A failure occurred in build().
    Aborting...