Search Criteria
Package Details: libelectron-electron-meta 37-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/libelectron-electron-meta.git (read-only, click to copy) |
|---|---|
| Package Base: | libelectron-electron-meta |
| Description: | A meta package for setting and controlling the electron versioning for LibElectron packages |
| Upstream URL: | None |
| Licenses: | GPL |
| Submitter: | gameslayer |
| Maintainer: | gameslayer |
| Last Packager: | gameslayer |
| Votes: | 0 |
| Popularity: | 0.000000 |
| First Submitted: | 2025-06-14 07:17 (UTC) |
| Last Updated: | 2025-07-10 08:50 (UTC) |
Latest Comments
gameslayer commented on 2025-06-14 08:50 (UTC)
Yes for now as I am transitioning from using electron from npm in libelectron to using the repo package of electron. Please read my news post for more information :)
https://coreybruce.netlify.app/news/plans-to-eventually-decouple-electron-from-libelectron-transition-24-4-2025
oech3 commented on 2025-06-14 08:45 (UTC)
OK. But
libelectroninstall doubleelectronbinary since it also requires*-castlab-bin.gameslayer commented on 2025-06-14 08:44 (UTC) (edited on 2025-06-14 08:46 (UTC) by gameslayer)
Hey this is a separate meta package is specifically for my AUR packages to manage the electron versioning for all my software that uses electron and libelectron. The reason I made this was so I had better control over the electron version in case anything goes wrong. I wanted to separate electron and the package dependencies from each other so I can update the electron dependencies, libelectron dependencies and have electron and electron-castlab as it's own seperate packages
oech3 commented on 2025-06-14 08:33 (UTC)
electronmeta symlink package exists. But is it impossible to merge this tolibelectron?