From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: Git spurious dependency: rsync
Date: Fri, 19 Sep 2014 21:35:00 -0000 [thread overview]
Message-ID: <20140919203006.GA22543@dinwoodie.org> (raw)
In-Reply-To: <1411147083.4932.3.camel@YAAKOV04>
On Fri, Sep 19, 2014 at 12:18:03PM -0500, Yaakov Selkowitz wrote:
> On Fri, 2014-09-19 at 11:56 -0500, René Berber wrote:
> > Updating cygwin today git version 2.1.0-1 is pulling rsync.
> >
> > From git's documentation (i.e. no mention of rsync):
> >
> > "To install Git, you need to have the following libraries that Git
> > depends on: curl, zlib, openssl, expat, and libiconv."
> >
> > There's also no mention on the release notes.
> >
> > Is this a dependency error?
>
> No, rsync is required for git archimport.
Also, (I suspect) more commonly, for the rsync protocol used for
git-clone and friends. See under "Git URLs" in `git help clone`.
If you're installing Git by compiling it from source, which is what I
assume the documentation is referring to, the requirements list is very
small; Git will happily compile without features that require the extra
libraries, just without access to those features. The version of Git
that's distributed pre-compiled from the Cygwin repository mirrors,
however, aims to be feature-complete rather than having minimal
requirements. As a result, it pulls in a lot of extra packages that
aren't necessary for basic Git functionality.
--
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:[~2014-09-19 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 20:42 [ANNOUNCEMENT] Updated: git-2.1.0-1 Adam Dinwoodie
2014-09-19 17:18 ` Git spurious dependency: rsync René Berber
2014-09-19 17:21 ` Yaakov Selkowitz
2014-09-19 21:35 ` Adam Dinwoodie [this message]
2014-09-20 4:36 ` Steven Penny
2014-09-21 2:14 ` Adam Dinwoodie
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=20140919203006.GA22543@dinwoodie.org \
--to=adam@dinwoodie.org \
--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).