git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jay Soffian <jaysoffian@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Michael Witten <mfwitten@gmail.com>, git <git@vger.kernel.org>
Subject: Oldest supported Perl version
Date: Mon, 20 Apr 2009 10:59:00 -0400	[thread overview]
Message-ID: <76718490904200759l24e1bd9exe0e1b60f7b2847a7@mail.gmail.com> (raw)

On Sun, Apr 19, 2009 at 9:58 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Sorry, I should have checked myself.  defined-or "//" is 5.8.1 or later.
>
> Now the real question was if we still support anything older, and if so
> what is the bottom version?
>
> I certainly can go with "5.8.1 or later", but I vaguely recall during the
> gitweb discussion we said anything without the utf-8 support is unusable
> for gitweb, but I think we also said that the rest of the git codebase
> should support running with something older (5.6.1, perhaps).

15 minutes of research:

* 2006-06-25 Junio C Hamano: "Tentatively let's say our cut-off point is
  somewhere around 5.6." --
  http://article.gmane.org/gmane.comp.version-control.git/22607

* 2008-05-30 Lea Wiemann: "Gitweb relies on Unicode support (e.g. "use
  Encode") and will continue to be compatible with 5.8 and 5.10 only" --
  http://article.gmane.org/gmane.comp.version-control.git/83339

* 2008-08-13 Lea Wiemann: "This makes Git.pm dependent on Perl 5.6.1. Some
  tests (like t3701-add-interactive.sh) seem to work with pretty much any Perl
  version out there, and requiring File::Spec changes this" --
  http://article.gmane.org/gmane.comp.version-control.git/92260

* 2008-08-15 Marcus Griep: "Git.pm: Make File::Spec and File::Temp requirement
  lazy" -- c14c8ce

* 2008-08-30 Junio C Hamano: "I agree we should say we rely on 5.6 or newer."
  -- http://article.gmane.org/gmane.comp.version-control.git/94399

* 2008-09-01 Junio C Hamano: "I personally think it is probably Ok to declare
  that we do depend on 5.8" --
  http://article.gmane.org/gmane.comp.version-control.git/94523


So here's my take-away. For the *.perl scripts and gitweb, it's 5.8.0. For the
test suite and Git.pm, all Perl versions are theoretically supported, but for
practical purposes, it may be 5.6.0.

Whatever is decided this time, perhaps it should be burned into the tops of
the *.perl scripts (i.e. "require 5.008;"). It should also be added to
CodingGuidelines. You know, so this conversation doesn't keep recurring. :-)

j.

             reply	other threads:[~2009-04-20 15:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 14:59 Jay Soffian [this message]
2009-04-20 15:40 ` [PATCH RFC3.5 04/12] send-email: Verification for --smtp-server and --smpt-server-port Michael Witten
2009-04-20 15:43 ` Oldest supported Perl version Michael Witten
2009-04-20 15:51   ` Jay Soffian
2009-04-20 16:18 ` H.Merijn Brand
2009-04-20 17:29   ` Johannes Schindelin
2009-04-20 21:07     ` H.Merijn Brand
2009-04-20 17:59 ` Jakub Narebski
2009-04-20 18:27   ` Jay Soffian
2009-04-20 18:32     ` Jay Soffian
2009-04-20 18:40       ` Michael Witten
2009-04-20 19:11         ` Johannes Schindelin
2009-04-20 19:58           ` Michael Witten
2009-04-20 21:10   ` H.Merijn Brand
2009-04-20 22:38     ` Michael Witten
2009-04-20 22:39       ` Michael Witten
2009-04-20 22:56         ` H.Merijn Brand
2009-04-21  3:08 ` Jeff King

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=76718490904200759l24e1bd9exe0e1b60f7b2847a7@mail.gmail.com \
    --to=jaysoffian@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mfwitten@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).