Always install bin versions of Electron by default?

So, Electron apps, amirite? I’m not exactly a fan, but need a couple of them.
Apparently, this means that at many a system update, I have to wait for Electron to compile from source, it takes many hours. The funny thing is, I don’t remember installations ever taking that long (i.e. it never seems like the whole thing is being compiled when I first install it, or I’d have noticed), just updates.

I’m looking for
a) a way to find out which package caused that source code version of Electron to be installed (as opposed to the binaries one), so I can possibly replace it.
b) a way to make sure I don’t install this stuff in the future.

  1. Is there way to ensure that, whenever a package has an Electron dependency, the bin version is installed rather than the source code one?
  2. I have many packages installed from chaotic-aur, only a couple from AUR. Are the chaotic-aur packages all pre-compiled?

Yes.
For AUR packages, everything depends on the packaging made by the maintainer.
If a package has dependency on electron packages which have a bin version available, this should be mentioned in the PKGBUILD and you should be able to use it when you compile.
In general, check the dependencies of you current and future packages.

5 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.