nodejs ships with corepack behind an default configure flag (--with-corepack). However, currently to use corepack with nodejs, the user has to manually enable corepack via `corepack enable`, which ends up creating symlinks in `/usr/bin` thus polluting it. It would be better to expose corepack as a USE flag, and create the symlinks as part of the install phase. Reproducible: Always
Created attachment 864052 [details, diff] Support for corepack as a useflag This patch enables corepack as a useflag thus making it optional, blocks installation of yarn if enabled, and installs the symlinks as part of the ebuild install phase to allow portage to track ownership of binaries.
Additional information on the feature here https://github.com/nodejs/node/blob/main/doc/api/corepack.md
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d10165aee072a96e13c6f1c84cca54e74e90f55d commit d10165aee072a96e13c6f1c84cca54e74e90f55d Author: William Hubbs <williamh@gentoo.org> AuthorDate: 2023-07-27 16:59:05 +0000 Commit: William Hubbs <williamh@gentoo.org> CommitDate: 2023-07-27 16:59:05 +0000 net-libs/nodejs: support the corepack experimental pkg management tool Closes: https://bugs.gentoo.org/908685 Signed-off-by: William Hubbs <williamh@gentoo.org> net-libs/nodejs/metadata.xml | 1 + 1 file changed, 1 insertion(+)
