devel/electron37: Update to 37.10.3
While here:
- switch to use USE_ELECTRON features of electron.mk for specifying
node package manager, pre-fetching necessary node modules, and
extracting the node modules into appropriate directories
- use USES=display for starting/stopping display server on testing
- specify TEST_ENV instead of listing env vars in test target
Changelog: https://github.com/electron/electron/releases/tag/v37.10.3
Reported by: GitHub (watch releases)
editors/emacs-devel: Pin to GCC 13
Build fails on some FreeBSD versions with GCC 14, which is about to
become GCC_DEFAULT. Pin to GCC 13 until the issue is fixed.
PR: 288303
Tested by: jrm
editors/emacs: Pin to GCC 13
Build fails on some FreeBSD versions with GCC 14, which is about to
become GCC_DEFAULT. Pin to GCC 13 until the issue is fixed.
PR: 288303
Reported by: yasu
Tested by: yasu, jrm
sysutils/desktop-installer: Update to 1.1.1.13
Support multiple versions of virtualbox guest additions
Offer to install popular shells
Improve user guidance on virtual consoles, switching to latest packages
Reported by: G Perrin
Mk/Uses: Add electron.mk and companion scripts
electron.mk and companion scripts for making it easier to port
Electron-based applications.
The electron.mk addresses the following obstacles in porting:
- Need to adapt to different node package managers used in a
project (npm, yarn, and pnpm)
Different package managers have different commands and options. With
electron.mk, porters don't have to worry about those differences
using USE_ELECTRON=npm feature.
- Need to create an archive of necessary node modules and host the
file somewhere online
An Electron-based project usually needs to install node modules
using "npm install" command during the build phase. We can't allow
[17 lines not shown]