From: Andrey Repin <anrdaemon@yandex.ru>
To: Houder <houder@xs4all.nl>, cygwin@cygwin.com
Subject: Re: snapshots (archive files) are too big ... Why?
Date: Sat, 23 Jan 2016 18:10:00 -0000 [thread overview]
Message-ID: <1211985131.20160123172147@yandex.ru> (raw)
In-Reply-To: <ed7dd3377a4cc1aa59001d627c7237ad@xs4all.nl>
Greetings, Houder!
> Just curious if there is a reason ...
> I was able to extract cygpath.exe from cygwin-inst-20160121.tar.xz
> (snapshots)
> in order to test your last modification to cygpath.cc. No problem here.
> However, when examining the contents of the archive, I was surprised to
> find
> the SAME version of cygpath.exe at least three times ...
> The size of cygwin-inst-<date>.tar.xz (and cygwin-src-<date>.tar.xz) has
> grown
> (suddenly) by a factor of 3 or 4 since 2015-07-20 ...
> The same applies to winsup-src-<date>.tar.xz (since 2016-01-15) ...
> In all cases it is because the archive contains the SAME version of a
> file at
> least three times (as far as I can tell).
> To summarize: No, I am not reporting a problem here; I am just _curious_
> as to
> why these archive are so much bigger than they (apparently) need to be
> ...
But this is actually a problem.
http://cygwin.com/snapshots/x86/cygwin-inst-20160121.tar
All tools reporting from 3 to 5 entries of each file in the archive.
--
With best regards,
Andrey Repin
Saturday, January 23, 2016 17:17:59
Sorry for my terrible english...
--
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 prev parent reply other threads:[~2016-01-23 14:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 14:35 Houder
2016-01-23 17:35 ` Andrey Repin
2016-01-23 18:10 ` Andrey Repin [this message]
2016-01-23 19:25 ` Houder
2016-01-23 20:13 ` Corinna Vinschen
2016-01-23 20:18 ` Houder
2016-01-23 21:56 ` Corinna Vinschen
2016-01-23 23:31 ` Houder
2016-01-24 10:12 ` Achim Gratz
2016-01-24 10:28 ` Houder
2016-01-24 1:22 ` Achim Gratz
2016-01-24 17:55 ` Corinna Vinschen
2016-01-24 18:36 ` Achim Gratz
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=1211985131.20160123172147@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=houder@xs4all.nl \
/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).