From: Junio C Hamano <junkio@cox.net>
To: "Martin Langhoff" <martin.langhoff@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Cygwin playbook?
Date: Thu, 07 Sep 2006 01:07:28 -0700 [thread overview]
Message-ID: <7vwt8g2j7j.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <46a038f90609070018k319b748cmae7a9b30da45b3b6@mail.gmail.com> (Martin Langhoff's message of "Thu, 7 Sep 2006 19:18:10 +1200")
"Martin Langhoff" <martin.langhoff@gmail.com> writes:
> Sorry to ask this... Are you sure? Vanilla base setup with no extra
> packages getting gcc and various -dev packages? Perhaps there is a
> 'developer' profile during install that gets you a reasonable kit?
What I meant was "readily available", not "installed by default".
> About 5 minutes ago I managed to get limited access (non-root, cannot
> install packages) to a cygwin env using rdesktop. It did have gcc and
> make, but make bombed out with a missing libcurl and openssl header
> files. IIRC, diff3/merge isn't in the base install either.
It is in rcs as usual ;-).
> In debian I can look at apt-cache show git-core to get a quick
> overview of dependencies but here I'm lost :(
The packaging was pretty much similar and I could guess from
apt-cache show git-core output indeed ;-).
next prev parent reply other threads:[~2006-09-07 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 4:59 Cygwin playbook? Martin Langhoff
2006-09-07 6:59 ` Junio C Hamano
2006-09-07 7:18 ` Martin Langhoff
2006-09-07 8:07 ` Junio C Hamano [this message]
2006-09-07 10:37 ` Martin Langhoff
2006-09-07 14:22 ` Christopher Faylor
2006-09-07 7:27 ` Shawn Pearce
2006-09-07 14:23 ` Christopher Faylor
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=7vwt8g2j7j.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.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 NNTP newsgroup(s).