Arch Linux User Repository

@je-vv the line with export npm_config_cache="$srcdir/npm_cache" should be equivalent to this – doesn't it work as I thought it did?

@lsf or @SamWhited, could you please add --cache "${srcdir}/npm-cache" or something similar so that npm and npx don't pollute the FS with bloated stuff? Thanks !

@gok: That's quite strange indeed – no idea why this could be. But still, great to hear that you could get it to build now! :)

When intially trying to build jitsi-meet-desktop 2.8.3-1 with plain makepkg on my system, it hung at building the robotjs dependency, like @milaq and @DAMO238 reported. Then I tried to build jitsi-meet-desktop 2.8.3-1 in a clean chroot (by running the following command, in a directory where I downloaded the jisti-meet-desktop PKGBUILD: extra-x86_64-build -- -I /path/to/nvm-0.37.2-1-any.pkg.tar.zst, where nvm 0.37.2-1 is the latest version currently in AUR), which worked.

The weird thing is that, after a 1st successful building of jitsi-meet-desktop 2.8.3-1 in a clean chroot, re-building it with plain makepkg now works, and I don't know why. I don't have time to dig into this at the moment. I will try to understand why this happens next time there is a jitsi-meet-desktop update.

Have you tried building it in a clean chroot to make sure it's not some enviroment / system specific issue? https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_clean_chroot

(I still can't reproduce it, neither in a clean chroot, docker or with plain makepkg).

I also have the hang at robotjs. I have tried using both nvm and nvm-git from the aur, neither of which worked.

Always hangs at building robotjs dependency for me. As @gok suggested, I've made sure that I have the latest nvm version installed (0.37.2-1) but to no avail.

@lsf, understood, thanks !

@je-vv:

Unfortunately: not easily.

Basically we'd need a more recent version of gyp for that.

In some cases, this can easily be done, if it's a direct (npm) dependency and nothing else depends on it (like in signal-desktop, for example: https://github.com/archlinux/svntogit-community/blob/packages/signal-desktop/trunk/PKGBUILD#L40).

In the case of this package though, it's a dependency of a dependency of a dependency (jitsi-meet-electron has jitsi-meet-electron-utils as a dependency, which has prebuild as a dependency (as a dev-dependency directly, or as a dependency indirectly by robotjs/prebuild-install requiring it), which (finally!) has node-gyp as a dependency – at ^3.0.3: https://github.com/jitsi/jitsi-meet-electron-utils/blob/master/package-lock.json#L2807. So in this case we'd have to somehow modify something deep in dependencies that are only pulled during building and do this once some are pulled while others aren't…

This might be possible with something like https://www.npmjs.com/package/patch-package, but (imho) it's just not worth the effort; just regular packaging of nodejs-/electron-based packages is already horrible enough ;)

If you just want to avoid cluttering your system with python2, it might be an option to build in a chroot or to use an AUR helper that offers to automatically remove make dependencies after building (like yay or paru, for example).

Any way to remove the python2 make dependency? Perhaps python can be used instead with some changes? Thanks!