Why doesn’t OpenSUSE build this as an noarch package.
After bulding the RPM there is over 17000 files, while the RPM built by yarn themself have only 13 files.
Why doesn’t OpenSUSE build this as an noarch package.
After bulding the RPM there is over 17000 files, while the RPM built by
yarn themself have only 13 files.
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.3|GNOME 3.20.2|4.4.104-39-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Hi
No since it’s linking files that it copies into the lib dir, you would just need to copy the yarn.js files over to /usr/bin and soft link and fix up the %files section.
If you do that then you would also need to add the following line after BuildRoot:;
Nothing, but 17000 files… unnecessary big. Yarn itself is much smaller.
We need to provide yarn with our SLES12 and those 2 Fedora people in my company complains about the complexity of SUSE yarn package compared to the one from Fedora.
Seems the supporting files are downloaded/installed using yarn itself.
Running yarn install fetches the necessary packages and stores it under node_modules/ in the project directory.
Hi
So one way or the other the files arrive… openSUSE maintainers have just decided to include…
Perhaps even a little bit more secure since it comes as a complete package from source…