Arch Linux User Repository

@huantian You're right, and I completely agree with your naming idea for transparency (e.g. gdlauncher-legacy(-bin,-git) / gdlauncher-carbon-bin)

Since as it stands, you cannot build gdlauncher-carbon locally without API keys.

Please, pin information about this to save others from wasting time

1) Here's what the GDLauncher-Carbon/README.md says:

To be able to develop on GDLauncher Carbon locally, you will need to request an API key to api-keys@gdlauncher.com. Please include your github username and a short description of what you are planning to do with the API key.

2) And if you try to build the project you'll encounter this:

Downloading https://binaries.prisma.sh/all_commits/d6e67a83f971b175a593ccc12e15c4a757f93ffe/debian-openssl-3.4.x/query-engine.gz to /home/user/game/.cache/prisma/binaries/cli/4.8.0/d6e67a83f971b175a593ccc12e15c4a757f93ffe/prisma-query-engine-debian-openssl-3.4.x

thread 'main' panicked at /home/user/game/.cargo/git/checkouts/prisma-client-rust-fa967aa5ad0ec391/f71ad91/cli/src/binaries/mod.rs:145:9:

received code 404 Not Found from https://binaries.prisma.sh/all_commits/d6e67a83f971b175a593ccc12e15c4a757f93ffe/debian-openssl-3.4.x/query-engine.gz

"This object does not exist or is not publicly accessible at this URL. Check the URL of the object that you're looking for or contact the owner to enable Public access."

Edit: the last bit was unrelated to API key in README but the issue still remains, see below:

Please show your support and follow the discussion in:

https://github.com/gorilla-devs/GDLauncher-Carbon/issues/388

I have had a conversation with the developer. I now have enough information to make a build without error telemetry, no CurseForge, and probably no Modrinth support. I will work on getting that building soon.

received code 404 Not Found from https://binaries.prisma.sh/all_commits/d6e67a83f971b175a593ccc12e15c4a757f93ffe/debian-openssl-3.4.x/query-engine.gz

This can be mitigated by spoofing your OpenSSL version. You can do so by adding the following file (with execution permissions) named openssl to your PATH while building.

# !/bin/bash
echo "OpenSSL 3.0.0 9 Apr 2024 (Library: OpenSSL 3.0.0 9 Apr 2024)"

The query engine simply does not exist for the OpenSSL version that Arch Linux uses.

Considering that gdlauncher-carbon in its current form requires an API key for local builds, I've opted to submit a request here in the hopes of seeing this changed in the future:

https://github.com/gorilla-devs/GDLauncher-Carbon/issues/388

@huantian You're right, and I completely agree with your naming idea for transparency (e.g. gdlauncher-legacy(-bin,-git) / gdlauncher-carbon-bin)

Since as it stands, you cannot build gdlauncher-carbon locally without API keys.

Please, pin information about this to save others from wasting time

1) Here's what the GDLauncher-Carbon/README.md says:

To be able to develop on GDLauncher Carbon locally, you will need to request an API key to api-keys@gdlauncher.com. Please include your github username and a short description of what you are planning to do with the API key.

2) And if you try to build the project you'll encounter this:

Downloading https://binaries.prisma.sh/all_commits/d6e67a83f971b175a593ccc12e15c4a757f93ffe/debian-openssl-3.4.x/query-engine.gz to /home/user/game/.cache/prisma/binaries/cli/4.8.0/d6e67a83f971b175a593ccc12e15c4a757f93ffe/prisma-query-engine-debian-openssl-3.4.x

thread 'main' panicked at /home/user/game/.cargo/git/checkouts/prisma-client-rust-fa967aa5ad0ec391/f71ad91/cli/src/binaries/mod.rs:145:9:

received code 404 Not Found from https://binaries.prisma.sh/all_commits/d6e67a83f971b175a593ccc12e15c4a757f93ffe/debian-openssl-3.4.x/query-engine.gz

"This object does not exist or is not publicly accessible at this URL. Check the URL of the object that you're looking for or contact the owner to enable Public access."

Edit: the last bit was unrelated to API key in README but the issue still remains, see below:

Please show your support and follow the discussion in:

https://github.com/gorilla-devs/GDLauncher-Carbon/issues/388

Former maintainer of these AUR packages here, I’d like to mention that the new rebrand and rewrite that the launcher has gone through resulted in essentially a new launcher which is under a proprietary license. It’s not really feasible to build it from source with a source package on the AUR anymore since we’d need API keys for their backend to do so.

The main issue isn’t building to binary vs appimage here, but rather that the way they’ve structured their project, we can’t build it at all :( such is the leaving OSS pipeline.

Thus, I propose we should leave the gdlauncher(-bin,-git) packages pointing to the old launcher, and only provide a gdlauncher-carbon-bin package for Carbon.

Now he wants to use modpacks so I figured a modern client would do the trick.

Note that gdlauncher-bin does just work. It is sometimes a little out of date, but it generally does the trick. Also note that the gdlauncher package is a legacy version, and should no longer be used.

I do not believe that I'm able to build to binary instead, but I'll see what I can do.

Keep us posted!

I just got my 10yo brother into Linux and he's in awe. Now he wants to use modpacks so I figured a modern client would do the trick.

I'll take a shot at trying to build carbon to see how far I can get

Aren't you able to provide just the regular binary

The dev's build system for Linux (pnpm iirc) builds directly to an AppImage. I do not believe that I'm able to build to binary instead, but I'll see what I can do.

I have gotten it to compile to a binary [..] This has lead to the build succeeding, but the resulting AppImage not working.

Awesome

Aren't you able to provide just the regular binary in this PKGBUILD which uses host's dependencies, instead of packaging it as AppImage?

(AppImages are a headache and don't benefit from Pacman updates. IMO, AppImages version would be better off as dedicated package like gdlauncher-carbon instead of being provided in a -git PKGBUILD)