-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
A plain tar.gz archive should be made available for downloading and packaging for Linux/*NIX #4842
Comments
Largely for the purpose of illustrating this issue, I've put my Arch package source (forked from the AUR) and Dockerfile up on GitHub here. |
Marking as a feature request. Creating a source distribution that will allow users to build the CLI v2 themselves is something want to do. |
Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one. |
Hi just wanted to check if there were plans of releasing a tar.gz (or Linux standard) version of the archive as mentioned in #6339 as well |
Please make a (signed, with checksums) .tar.gz or similar archive available for Linux/*NIX distributions instead of (or, at least, as well as) the command-line installer. I have several reasons for requesting this:
FROM
ubuntu:18.04
was 185MB. The Arch package is 69MB.2.0.0dev3
: a few days ago, it was giving2.0.0dev2
.groff
andless
persistently installed in order to use thehelp
commands.As an example, when packaging your code for Arch Linux, I've had to run operations like this:
You can see how I have to remove your symlinks and re-create them in the fakeroot to get correct paths.
Please see similar arguments e.g. here and various other places around the WWW.
The text was updated successfully, but these errors were encountered: