X-Spam-Check-By: sourceware.org Date: Tue, 23 Jan 2007 09:40:28 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Hard links in tar, not untaring as expected Message-ID: <20070123084028.GF27843@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3D848382FB72E249812901444C6BDB1D0A653DB1@mail.timesys.com> <45B5812C.7040605@byu.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45B5812C.7040605@byu.net> User-Agent: Mutt/1.4.2.2i Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Jan 22 20:29, Eric Blake wrote: > But speaking of hard links and tar, I find it annoying that setup.exe > won't even try to create hard links when a tar file requests them. A good > example of this is the git-1.4.4.4-1.tar.gz2 package - it contains 55 hard > links to usr/bin/git.exe, but setup.exe unpacks it into 55 separate files, > rather than a single file, thus occupying 26 megabytes more hard drive > space than strictly necessary on NTFS. Why don't you just patch setup to do that? You are maintainer of the original tar code, so you would not be the worst choice to pump up the tar lib code in setup. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/