Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need a packaging guide #5628

Closed
cyqsimon opened this issue Jul 31, 2023 · 0 comments
Closed

Need a packaging guide #5628

cyqsimon opened this issue Jul 31, 2023 · 0 comments

Comments

@cyqsimon
Copy link

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.

@yarnpkg yarnpkg locked and limited conversation to collaborators Jul 31, 2023
@arcanis arcanis converted this issue into discussion #5629 Jul 31, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant