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

maketgz: switch to xz instead of lzma #1604

Closed
wants to merge 1 commit into from
Closed

maketgz: switch to xz instead of lzma #1604

wants to merge 1 commit into from

Conversation

bagder
Copy link
Member

@bagder bagder commented Jun 21, 2017

The compressed output size seems to be a tad bit smaller, but generally
xz seems more preferred these days and is used directly by for example
gentoo instead of bz2.

"Users of LZMA Utils should move to XZ Utils" =>
https://tukaani.org/lzma/

The compressed output size seems to be a tad bit smaller, but generally
xz seems more preferred these days and is used directly by for example
gentoo instead of bz2.

"Users of LZMA Utils should move to XZ Utils" =>
https://tukaani.org/lzma/
@coveralls
Copy link

Coverage Status

Coverage increased (+0.008%) to 73.793% when pulling 8c07a53 on bagder/xz into 8de8f4e on master.

@bagder bagder closed this in 0537238 Jun 21, 2017
@bagder bagder deleted the bagder/xz branch June 21, 2017 22:53
@dfandrich
Copy link
Contributor

The daily snapshots stopped being built shortly after this was committed. Coincidence?

And on an unrelated note, the tradeoff for using xz -9 is much worse than for gzip. It drastically increases the amount of RAM required for decompressing, without improving compression for smaller-sized files. The docs say "it is good to avoid using the presets -7 ... -9 when there's no real need for them."

@bagder
Copy link
Member Author

bagder commented Jun 23, 2017

Coincidence?

Nope, I managed to break the script when I updated it for the new extension! Fixed now.

the tradeoff for using xz -9 is much worse than for gzip

I changed it to -6e now, as that compresses almost as good. Thanks!

@lock lock bot locked as resolved and limited conversation to collaborators Jan 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants