Skip to content
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

Suggestion: Use tar or zip for release artifacts #548

Open
burdiyan opened this issue Jan 24, 2024 · 0 comments
Open

Suggestion: Use tar or zip for release artifacts #548

burdiyan opened this issue Jan 24, 2024 · 0 comments

Comments

@burdiyan
Copy link

I'm thinking about using Buck2 for a project, and the fact that binary releases are compressed with zstd is making the developer experience and initial onboarding this much more complicated. Unlike tar or zip, most people don't have zstd CLI installed on their machine, and some even might not know what it is.

My idea is to provide a superb DX, where you'd only need buck2 installed to successfully run the build.

Is there any specific reason for using zstd for Buck2 releases over something more conventional, except the fact that zstd was also created at Meta 🙂?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant