From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 130579 invoked by alias); 23 Jan 2016 18:10:56 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 130564 invoked by uid 89); 23 Jan 2016 18:10:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-92.8 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,KHOP_DYNAMIC,RCVD_IN_BRBL_LASTEXT,RCVD_IN_PBL,RDNS_DYNAMIC,USER_IN_WHITELIST autolearn=no version=3.3.2 spammy=Maintainer, H*i:sk:ed7dd33, Hx-languages-length:1586, H*R:U*cygwin X-HELO: calimero.vinschen.de Received: from ipbcc05c50.dynamic.kabel-deutschland.de (HELO calimero.vinschen.de) (188.192.92.80) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 23 Jan 2016 18:10:55 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 0B773A803D9; Sat, 23 Jan 2016 19:10:53 +0100 (CET) Date: Sat, 23 Jan 2016 20:13:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: snapshots (archive files) are too big ... Why? Message-ID: <20160123181053.GF3268@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="dgjlcl3Tl+kb3YDk" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SW-Source: 2016-01/txt/msg00317.txt.bz2 --dgjlcl3Tl+kb3YDk Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1599 On Jan 23 13:59, Houder wrote: > Hi Corinna, >=20 > Just curious if there is a reason ... >=20 > 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. >=20 > However, when examining the contents of the archive, I was surprised to f= ind > the SAME version of cygpath.exe at least three times ... >=20 > The size of cygwin-inst-.tar.xz (and cygwin-src-.tar.xz) has > grown > (suddenly) by a factor of 3 or 4 since 2015-07-20 ... >=20 > The same applies to winsup-src-.tar.xz (since 2016-01-15) ... >=20 > 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). >=20 > 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 ... I found out why this happens, I just don't know why it only occurs since 2015-07-20. The reason is the script is using an expression along the lines of find ... | tar -T - --no-recursion -cjf ... It turns out that the --no-recursion option only works for me, if it comes *prior* to the expression specifying the filenames to archive. That is, I had to change the script to use find ... | tar --no-recursion -T - -cjf ... instead. Funny enough, `info tar' still contains an example using the original order... Thanks, Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --dgjlcl3Tl+kb3YDk Content-Type: application/pgp-signature; name="signature.asc" Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWo8IsAAoJEPU2Bp2uRE+gUTAQAIQZ9ApTQ9f4Cy+O3L3hZbou rJTK4kOQUiMx4QgvhbfzNlnFpidboCMSSiupHyw+jyevE5iH8tWWk6FRU8tSsAcf GkgMammaVDBwMtXNB5vtyeZnUxsGJMVtvq8OO6TwH8HDgvm5zGNEtPz24E2+YO4v PcmqGV1F0ZdQp1afj1FOSB1L8AXQiHHiBSIvoddtNFC3dLd6MXxafxLv2I80DyUx CxbM1f+AqvjRLJkfkB915ojhZfEF5Ag28htI/ZDBO+X69DoJeBNc8YLX2efffHgy UY7XHwl6iebz49cCv84zWVaVVqHzV42oPqdyEnAy5gX+RhimnrsPtIZutlwWlXPu 040Dlb7GGJOU+054303+N6jOSjAO1MicTjdluA3AewCTKgljMGGfMdWrxmeszeu/ mOtblSUEO6q8jzrG8q8+X81XPOa6ARMDbK5MBR11JjfsSndb8nn6D+KbNCmFPavf 6l4uD/kpp1XV7aGDOCts+OTbEwPVDuYJBEDBsZ1/Sn4t94tLtAOMeZRQBXpvuMBN hBz2EjeSAmHAw9Lpg47kc51HBhJfXjNYm22a/y3BQ1TDdxU9X6nQJaVwnM/p4K2t DLKoUxDzOGgxpkvTJLdB+pz+AvsAOPL3p9pc1Bq9f0XOz+mpZPubppMvteGKIgDV E/CJKPqtFjigNVCxCB6J =SySi -----END PGP SIGNATURE----- --dgjlcl3Tl+kb3YDk--