Package Details: heroic-games-launcher 2.16.0-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: GPL-3.0-only
Submitter: FabioLolix
Maintainer: FabioLolix
Last Packager: FabioLolix
Votes: 27
Popularity: 3.09
First Submitted: 2022-07-18 20:20 (UTC)
Last Updated: 2025-03-02 17:48 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

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

dataprolet commented on 2023-04-14 11:31 (UTC)

The installation of this package fails, when you have the binary version already installed. Please add conflict with heroic-games-launcher-bin.

JesseSteele commented on 2023-03-09 23:56 (UTC)

@flaviofearn I'm just another user as far as this package goes, and it doesn't bother me to have these three packages as options because their differences are well explained. But, it's is even better to know that you are the dev for that awesome software. You might just comment on the -bin package to let the world know that you are the the dev/maintainer for that one. (Having alternatives is a compliment because it means you're a thing that's sought after.)

haxie commented on 2022-12-08 16:00 (UTC)

@flaviofearn Hiya, Having multiple versions on the AUR is fine, as long as they're named correctly, and as this one already is, it makes sense to keep it up!

Some users may wish to compile locally, so that they can be sure that the software they are running is indeed the one from the codebase they expect, so for those users, a regular <package> AUR entry is made For those who wish to have the latest and greatest at all times, <package>-git is made, and for those who are fine with downloading a precompiled binary from the developer, a <package>-bin is made.

Hope this helps!

« First ‹ Previous 1 2 3 4 5 Next › Last »