Package Details: heroic-games-launcher 2.14.1-1

Git Clone URL: https://aur.archlinux.org/heroic-games-launcher.git (read-only, click to copy)
Package Base: heroic-games-launcher
Description: Native GOG, Epic Games and Amazon games launcher for Linux
Upstream URL: https://heroicgameslauncher.com/
Licenses: GPL3
Submitter: FabioLolix
Maintainer: FabioLolix
Last Packager: FabioLolix
Votes: 16
Popularity: 2.53
First Submitted: 2022-07-18 20:20 (UTC)
Last Updated: 2024-04-09 12:07 (UTC)

Latest Comments

1 2 Next › Last »

Yamashiro commented on 2024-03-29 09:12 (UTC) (edited on 2024-03-29 09:13 (UTC) by Yamashiro)

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.

FabioLolix commented on 2024-01-07 18:11 (UTC)

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

Achilleus commented on 2024-01-07 17:57 (UTC)

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...



FabioLolix commented on 2023-12-23 17:16 (UTC)

@Achilleus can't reproduce; clean the package cache if there is. I have builded now with makepkg and with devtools before upload (from devtools package https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot using extra-x86_64-build for convenience), I tried to upload my builded package to sourceforge but the upload failed

Achilleus commented on 2023-12-23 16:44 (UTC)


$ LC_ALL=C makepkg -sic
==> Making package: heroic-games-launcher 2.11.0-1 (Sat Dec 23 17:42:41 2023)
==> 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'
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.68s.
==> 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.67s.
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...


FabioLolix commented on 2023-12-23 15:59 (UTC)

@Achilleus When I have time, updating pkgbuilds isn't my paid job

Achilleus commented on 2023-12-16 14:34 (UTC)

When PKGBUILD will be updated to 2.11?

FabioLolix commented on 2023-09-20 21:29 (UTC)

@cybrid this build a fixed version [note #tag=${pkgver} in source=() ] while -git one build the latest commit, none has to go

cybrid commented on 2023-09-20 12:48 (UTC)

I think it's this package and the -git that are essentially the same. Both point directly to the git repo, while -bin points to the release version. One of them should probably go.

FabioLolix commented on 2023-06-30 18:08 (UTC)

@proledatarian no, they have already been informed 3 times that they need to improve their pkgbuilds