Packaging pnpm v12 for openSUSE: The "@pnpm/exe.linux-x64" package is not installed, so pnpm has no native binary to run.
#17890
Replies: 2 comments 1 reply
|
Since v12 the The fix is to ship the platform package as a second source and install it next to the wrapper. Source0: https://registry.npmjs.org/pnpm/-/pnpm-%{version}.tgz
# one per arch you build for
Source1: https://registry.npmjs.org/@pnpm/exe.linux-x64/-/exe.linux-x64-%{version}.tgz
Source2: https://registry.npmjs.org/@pnpm/exe.linux-arm64/-/exe.linux-arm64-%{version}.tgz
# ppc64le -> exe.linux-ppc64, s390x -> exe.linux-s390x, riscv64 -> exe.linux-riscv64
%install
export npm_config_prefix=%{buildroot}%{_prefix}
%ifarch x86_64
npm install -g --offline %{SOURCE1}
%endif
%ifarch aarch64
npm install -g --offline %{SOURCE2}
%endif
npm install -g --offline --omit=optional %{SOURCE0}Install the platform package first, so it's already in Two things I'd avoid:
Also note that only glibc builds exist for ppc64le, s390x and riscv64, and big-endian ppc64 isn't supported at all. |
|
Since v12 pnpm is a Rust program, so the binary in What to build The CLI crate is ( What to install The binary is standalone. The npm wrapper's No node-gyp The one thing the npm package ships that the bare binary does not is a |
Uh oh!
There was an error while loading. Please reload this page.
Dear maintainers,
I am one of the package maintainers for the openSUSE pnpm package. Starting with v12, the packaging approach we used before does no longer work.
https://registry.npmjs.org/%{name}/-/%{name}-%{version}.tgznpm_config_prefix=/home/abuild/rpmbuild/BUILD/pnpm-%{version}-build/BUILDROOT/usrnpm install -g /home/abuild/rpmbuild/SOURCES/pnpm-%{version}.tgz%{version}.Starting with v12, we get an error during installation:
Any ideas how to solve this? I checked the documentation, but did not find any instructions fitting our usecase.
Do we need a different tarball? Different install command or other command line options?
Thanks in advance,
Johannes
All reactions