Arch Linux User Repository

Not sure why I forgot to comment here, but I've updated that PKGBUILD a while ago to use the official itch installer. The checksums verify that the installer matches upstream, and you get the latest itch app from the itch CDN.

I personally don't care much how it's done, but it's just a little bit bothersome to have one package out of my normal workflow. I format a lot of machines and always install itch (❤), I would like to continue being able to just add it to the list that I pipe to my package manager.

Since I do not care about the internals, and only about the surface, I'm fine with a package that just runs the installer.

I think it would be more sustainable to just download and run the installer, taking care of Arch-specific env variables and packaging conventions (install dir etc, assuming they apply at all, I have not looked into it).

If there is (and there is projected to be for a while) manpower enough to do both things like ainola suggests, that would naturally be the best of both worlds :)

Hey Arch users, itch v25 has finally released, and it comes with its own installer program: https://itch.io/app

I'm not sure what do about this package. I've crafted a .deb package that just installs the installer, https://github.com/itchio/itch-setup along with a few .desktop files, for shortcuts.

One option would be to have the AUR package compile itch-setup and set up the .desktop shortcuts, like the .deb package does. You can see the .deb building logic here: https://gist.github.com/fasterthanlime/2b1aa571bf7b680be2da13359bdb5c08

Another option would be to have the AUR package just download the latest itch-setup binary from https://broth.itch.ovh/itch-setup - this way the package wouldn't have to depend on a Go toolchain. It would just have the dependencies required to have the app run (no python, no grunt, no npm - just the few X and gtk libs).

What do you think of those options?

Hi, FrozenCow - Do you have any plans on updating this package? As it stands it does not build without manual intervention. If you are not interested in maintaining, I would be willing to take over.

Thanks!

Dependency nodejs-grunt-cli no longer exists. Looks like it's now nodejs-grunt.

I've just released v23.6.3, which should build cleanly on a fully-upgraded Arch. Let me know if you still have issues.

It appears the package for v23.6.2 just won't build if you have a recent enough nodejs installed (and this is Arch, so everybody has the latest node).

I'll look into releasing v23.6.3 tomorrow that depends on a more recent node-sass, even though there's absolutely nothing changed in v23.6.2 for Linux (see changelog: https://github.com/itchio/itch/releases/tag/v23.6.2 )

First error I see with 23.6.2-1 is: Cannot download "https://github.com/sass/node-sass/releases/download/v4.5.3/linux-x64-64_binding.node": HTTP error 404 Not Found

There is only linux-x64-11_binding.node to linux-x64-57_binding.node on that github page...

23.6.2 won't build fails here

Error: Exit code assertion failed, bailing out at $ (/home/af/.cache/pacaur/itch/src/itch-23.6.2/release/node_modules/munyx/index.js:19:11) at Object.<anonymous> (/home/af/.cache/pacaur/itch/src/itch-23.6.2/release/ci-compile.js:12:1) at Module._compile (internal/modules/cjs/loader.js:678:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:689:10) at Module.load (internal/modules/cjs/loader.js:589:32) at tryModuleLoad (internal/modules/cjs/loader.js:528:12) at Function.Module._load (internal/modules/cjs/loader.js:520:3) at Function.Module.runMain (internal/modules/cjs/loader.js:719:10) at startup (internal/bootstrap/node.js:228:19) at bootstrapNodeJSCore (internal/bootstrap/node.js:575:3)</anonymous>