You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this point yarn is independently packaged in almost every Linux distribution, see https://pkgs.org/search/?q=yarn. Hovever today I discovered, to my great surprise,that most if not all of them (including ArchLinux!) are still offering 1.22, which is very odd.
So naturally I submitted issues to the distros I use, and the good people at Fedora replied pretty quickly: https://bugzilla.redhat.com/show_bug.cgi?id=2227706#c1, saying that they "didn't really manage to understand how to build it from source". I linked to them an exampe of how an AUR package did it, but honestly its liberal use of cp -R * worries me. When I looked into the newest release tarball, it confused me whether the entry point should be directly packages/yarnpkg-cli/bin/yarn.js, or should it be scripts/bin/yarn, or should it be scripts/dist-scripts/yarn. I suspect the reason other distros haven't updated might be similar - they don't know what to do.
Therefore I think it would be a good idea for this repo to contain some kind of official documentation/recommendation/guides on how independent packagers should be packaging yarn 3.x. Thank you in advance for your effort.
The text was updated successfully, but these errors were encountered:
At this point yarn is independently packaged in almost every Linux distribution, see https://pkgs.org/search/?q=yarn. Hovever today I discovered, to my great surprise,that most if not all of them (including ArchLinux!) are still offering 1.22, which is very odd.
So naturally I submitted issues to the distros I use, and the good people at Fedora replied pretty quickly: https://bugzilla.redhat.com/show_bug.cgi?id=2227706#c1, saying that they "didn't really manage to understand how to build it from source". I linked to them an exampe of how an AUR package did it, but honestly its liberal use of
cp -R *
worries me. When I looked into the newest release tarball, it confused me whether the entry point should be directlypackages/yarnpkg-cli/bin/yarn.js
, or should it bescripts/bin/yarn
, or should it bescripts/dist-scripts/yarn
. I suspect the reason other distros haven't updated might be similar - they don't know what to do.Therefore I think it would be a good idea for this repo to contain some kind of official documentation/recommendation/guides on how independent packagers should be packaging yarn 3.x. Thank you in advance for your effort.
The text was updated successfully, but these errors were encountered: