git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "J.H." <warthog19@eaglescrag.net>
Cc: Rafael Garcia-Suarez <rgarciasuarez@gmail.com>,
	Petr Baudis <pasky@suse.cz>, Lea Wiemann <lewiemann@gmail.com>,
	Jakub Narebski <jnareb@gmail.com>,
	git@vger.kernel.org, Lars Hjemli <hjemli@gmail.com>
Subject: Re: Gitweb caching: Google Summer of Code project
Date: Fri, 30 May 2008 13:28:04 -0700	[thread overview]
Message-ID: <7vd4n3k04r.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 1212173779.26045.77.camel@localhost.localdomain

"J.H." <warthog19@eaglescrag.net> writes:

> On Fri, 2008-05-30 at 18:04 +0200, Rafael Garcia-Suarez wrote:
>> 2008/5/30 Petr Baudis <pasky@suse.cz>:
>> >
>> > Wow, and here I was wondering if requiring at least 5.6 was not too
>> > liberal. ;-) I believe 5.8 is the newest possible candidate though, it
>> > is still too widespread; e.g. Debian-wise, many servers run on Etch and
>> > are going to stay there even for quite some time after Lenny gets
>> > released. Heck, I still have accounts on plenty of Sarge machines. ;-)
>> > (Sarge seems to have Perl-5.8.4.)
>> 
>> I think 5.8.2 is a good _minimum_ perl to support. Before that one,
>> Unicode support is next to null (5.6 and below) or too buggy, and
>> gitweb needs that.

> I would agree - lets try and shoot for 5.8 as a baseline minimum (there
> are lots of people who are slow to upgrade, and it would be nice to be
> able for them to make use of newer gitweb's on things like Centos / RHEL
> 4

I do not think it is unreasonable to require recent Perl for a machine
that runs gitweb, as it is not something you would run on your "customer
site that needs to be ultra sta(b)le" nor on your "development machine
that needs to run the same version as that ultra sta(b)le customer
installation."  In other words, gitweb is primarily a developer tool, and
you can assume that people can afford to have a dedicated machine they can
update its Perl to recent version.

However, introducing dependency on 5.8 to any and all Git.pm users may
have a much wider impact.  Right now, these "use Git":

    git-add--interactive.perl
    git-cvsexportcommit.perl
    git-send-email.perl
    git-svn.perl

If you are doing development for some customer application whose end
product needs to land on a machine with a pre-5.8 Perl, it is conceivable
that you may pin the Perl running on that development machine to that old
version, say 5.6.  Introducing 5.8 dependency to Git.pm in such a way that
"use Git" from these fail might make these people somewhat unhappy.

  reply	other threads:[~2008-05-30 20:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27 18:03 Gitweb caching: Google Summer of Code project Lea Wiemann
2008-05-27 21:53 ` Jakub Narebski
2008-05-27 22:54   ` Lea Wiemann
2008-05-28 12:14     ` Jakub Narebski
2008-05-28 18:33       ` Lea Wiemann
2008-05-29 23:27         ` Jakub Narebski
2008-05-30  7:24           ` Lea Wiemann
2008-05-30 10:02             ` Jakub Narebski
2008-05-30 14:59               ` Lea Wiemann
2008-05-30 15:07                 ` Petr Baudis
2008-05-30 15:27                   ` Lea Wiemann
2008-05-30 15:38                     ` Petr Baudis
2008-05-30 16:04                       ` Rafael Garcia-Suarez
2008-05-30 18:56                         ` J.H.
2008-05-30 20:28                           ` Junio C Hamano [this message]
2008-05-30 21:32                             ` Lea Wiemann
2008-05-30 18:47                       ` Lea Wiemann
2008-05-31 10:15                     ` Jakub Narebski

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=7vd4n3k04r.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=hjemli@gmail.com \
    --cc=jnareb@gmail.com \
    --cc=lewiemann@gmail.com \
    --cc=pasky@suse.cz \
    --cc=rgarciasuarez@gmail.com \
    --cc=warthog19@eaglescrag.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 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).