git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Dessent <brian@dessent.net>
To: Reini Urban <rurban@x-ray.at>
Cc: git@vger.kernel.org
Subject: Re: shared lib+symlinks patch for cygwin
Date: Sun, 22 Jun 2008 01:10:31 -0700	[thread overview]
Message-ID: <485E08F7.ADE2290C@dessent.net> (raw)
In-Reply-To: 6910a60806220056i1dda7f4elb4e5c69cdeea3cf9@mail.gmail.com

Reini Urban wrote:

> esp. on cygwin where file hardlinks do not work as on linux.
> old bindir 5.8MB, new 2.7MB

Hard links work just fine on Cygwin, assuming the underlying volume is
NTFS.  What you probably mean to say is that the Cygwin setup.exe
program won't create hardlinks from the tarball when installing binary
packages.  But this could be worked around by creating the links with
'ln' in a postinstall script.  Then NTFS users would get the space
savings and FAT users would get copies.

Brian

  reply	other threads:[~2008-06-22  8:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-22  7:56 shared lib+symlinks patch for cygwin Reini Urban
2008-06-22  8:10 ` Brian Dessent [this message]
2008-06-22  8:19   ` Reini Urban

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=485E08F7.ADE2290C@dessent.net \
    --to=brian@dessent.net \
    --cc=git@vger.kernel.org \
    --cc=rurban@x-ray.at \
    /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 NNTP newsgroup(s).