From: "Jérôme Bouat" <jerome.bouat@laposte.net>
To: cygwin@cygwin.com
Subject: a few tar.xz packages are bigger than their uncompressed tar
Date: Sun, 24 Sep 2017 18:46:00 -0000 [thread overview]
Message-ID: <cc1a2cd5-a947-624e-4473-73151794a5d7@laposte.net> (raw)
Hello,
I looked into the local folder where the downloaded packages are saved before they are installed. I noticed that a few compressed archives files are using more size than their uncompressed form. For example, the libstdc++6-6.4.0-1.tar.xz file uses more space than its uncompressed tar file (on cygwin x86_64).
That is not surprising. All compression methods may sometimes inflate the final amount of data.
Would it be a way to keep the tar archive file uncompressed if the compressed form needs more space ?
Regards.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2017-09-24 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 18:46 Jérôme Bouat [this message]
2017-09-24 19:19 ` Marco Atzeri
2017-09-27 4:50 ` Andrey Repin
2017-10-05 18:56 ` Kaz Kylheku
2017-10-05 19:09 ` Jérôme Bouat
2017-10-05 19:10 ` Jérôme Bouat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cc1a2cd5-a947-624e-4473-73151794a5d7@laposte.net \
--to=jerome.bouat@laposte.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).