From: Brian Gernhardt <brian@gernhardtsoftware.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [RFC PATCH 2/2] INSTALL: Describe a few knobs from the Makefile
Date: Tue, 8 Sep 2009 20:12:06 -0400 [thread overview]
Message-ID: <9908511C-448F-4E52-84B0-4C6BED3DC1DD@gernhardtsoftware.com> (raw)
In-Reply-To: <7vy6opxjx8.fsf@alter.siamese.dyndns.org>
On Sep 8, 2009, at 4:26 PM, Junio C Hamano wrote:
> [rewrite suggestions snipped]
I'll re-roll this and the other INSTALL patch as per your suggested re-
wordings. I tried to add the minimum needed instead of changing
things, but many of your suggestions make sense. And since I'm in
here anyway, might as well change them.
> Brian Gernhardt <brian@gernhardtsoftware.com> writes:
>> + - "openssl". Unless you specify otherwise (with NO_OPENSSL),
>> + you'll get the SHA1 library from here.
>
> It is not very clear what will be affected by disabling this.
>
> - SHA-1 is not used from OpenSSL, as stated;
> - imap-send won't be able to talk over SSL;
>
> Do we still able to walk https:// URLs? If your cURL library is
> linked
> with gnutls I think we can, but I never tried the combination.
Glancing at http*.[ch], it looks like we depend on curl's ability to
speak https instead of using OpenSSL ourselves.
>> + - "perl" is used for several scripts that are useful, but not
>> + required for git (e.g. "git add -i" and "git difftool"). If you
>> + don't need the *.perl scripts or the library contained in perl/,
>> + then use NO_PERL.
>
> I do not think moving "Perl" this low in the requirement level is
> such a
> good idea, at least for now. I'd suggest movign it back immediately
> after
> POSIX-compliant shell, and would say something like this:
>
> - "Perl" is needed to use some of the features (e.g. preparing a
> partial commit using "git add -i/-p", interacting with svn
> repositories with "git svn"). If you can live without these,
> say NO_PERL.
>
> Maybe they are Ruby, github, and general acceptance by many open
> source
> projects these days, but it used to be that the initial entry points
> to
> git were "git cvsimport" and "git svn" for a surprisingly large
> number of
> people.
I didn't move it this low so much as not move it when I moved the
POSIX shell requirement that we can't live without. Although I use
git-svn on a regular basis, I don't think of it as core, but you're
right that it's one of the main tools for many users. Will move.
~~ Brian
next prev parent reply other threads:[~2009-09-09 0:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 15:55 [PATCH 1/2] INSTALL: Update description of our SHA-1 code Brian Gernhardt
2009-09-08 15:55 ` [RFC PATCH 2/2] INSTALL: Describe a few knobs from the Makefile Brian Gernhardt
2009-09-08 20:26 ` Junio C Hamano
2009-09-09 0:12 ` Brian Gernhardt [this message]
2009-09-08 20:21 ` [PATCH 1/2] INSTALL: Update description of our SHA-1 code Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9908511C-448F-4E52-84B0-4C6BED3DC1DD@gernhardtsoftware.com \
--to=brian@gernhardtsoftware.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).