From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
"Kyle J. McKay" <mackyle@gmail.com>,
Johan Herland <johan@herland.net>,
git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.0.0-rc0
Date: Tue, 22 Apr 2014 15:47:48 -0700 [thread overview]
Message-ID: <xmqqbnvt2d7v.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140422222519.GC144079@vauxhall.crustytoothpaste.net> (brian m. carlson's message of "Tue, 22 Apr 2014 22:25:19 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> On Tue, Apr 22, 2014 at 03:11:48PM -0700, Jonathan Nieder wrote:
>> Another possibility would be to require Perl 5.8.9 or newer. It was
>> released in 2008.
>
> RHEL 5 and CentOS 5 are still shipping with 5.8.8. They are still
> security-supported until 2017, and believe it or not people still
> develop on them. I am personally fine with this change, though.
>
> What we could do instead is simply require a newer version of
> Getopt::Long, which would let people continue using their ancient OSes
> and install a newer version from CPAN if necessary. It's also the
> proper way to specify the dependency.
Yes, but if its inability to properly grok --option="" is the only
reason we want to add a dependency, wouldn't it suffice to simply
state in the documentation (1) how to recognise the symptom to see
if the version the user has is too old, e.g. "if you see this error
message", "run 'perl -v' to see if your perl is older than X",
etc. and (2) how to work it around, i.e. "instead of giving an empty
value with --option='', say --option ''"?
next prev parent reply other threads:[~2014-04-22 22:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 19:37 [ANNOUNCE] Git v2.0.0-rc0 Junio C Hamano
2014-04-19 1:13 ` Johan Herland
2014-04-19 7:20 ` Junio C Hamano
2014-04-20 19:08 ` Felipe Contreras
2014-04-20 21:14 ` Junio C Hamano
2014-04-22 11:16 ` Kyle J. McKay
2014-04-22 18:58 ` Jonathan Nieder
2014-04-22 20:12 ` Junio C Hamano
2014-04-22 21:00 ` Jonathan Nieder
2014-04-22 21:26 ` Junio C Hamano
2014-04-22 22:11 ` Jonathan Nieder
2014-04-22 22:25 ` brian m. carlson
2014-04-22 22:47 ` Junio C Hamano [this message]
2014-04-23 7:33 ` Johan Herland
2014-04-23 16:40 ` Junio C Hamano
2014-04-22 19:56 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqbnvt2d7v.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
--cc=jrnieder@gmail.com \
--cc=mackyle@gmail.com \
--cc=sandals@crustytoothpaste.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.