All of lore.kernel.org
 help / color / mirror / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Perl version support
Date: 23 Nov 2005 11:59:30 -0800	[thread overview]
Message-ID: <86br0bm8yl.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <7vwtiz4053.fsf@assigned-by-dhcp.cox.net>

>>>>> "Junio" == Junio C Hamano <junkio@cox.net> writes:

Junio> I think the target market is people who use whatever POSIXy
Junio> systems for their own work.  To them, git and its dependencies
Junio> are merely tools to get their job done, and while they might be
Junio> capable and even willing to match the version requirements if it
Junio> is absolutely necessary, they'd rather spend their time on what
Junio> they do best (i.e. write software or documentation or whatever,
Junio> whose changes are to be managed by git), than installing or
Junio> upgrading base software just to satisfy git.  And I'd like to
Junio> see their time spent on what they do best, instead of caring and
Junio> feeding of git, too.

Yes, this is why I keep pointing out GNU tools being used instead of
POSIXy versions. :)  Mostly because they break on either my Darwin
laptop or my OpenBSD host server.

Junio> So in that sense, excluding 75% of people with "5.8 only" is not
Junio> acceptable at all, and covering 75% with "5.6 or better" might
Junio> be good enough, at least as a starter.

I think we're in agreement.

>> If you'd like, I can review all the Perl code with a tool that
>> determines the minimum Perl version, and provide patches to bring the
>> code to 5.5 level.

Junio> If it is not too much trouble, I'd appreciate it, at least the
Junio> first half that can be done without taking too much of your time.
Junio> Is it a mechanical "lint" like thing, that says "line 47 you
Junio> have list form of pipe open -- that's 5.8 and better"?

The "perlver" tool installed with the "Perl::MinimumVersion" module
from the CPAN will do about 80% of it.  The other 20% are things
that I can use my brain for.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

  reply	other threads:[~2005-11-23 19:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-23  5:41 [PATCH] git-mv is not able to handle big directories Alexander Litvinov
2005-11-23  6:14 ` Junio C Hamano
2005-11-23  6:32   ` Junio C Hamano
2005-11-23  7:55     ` Randal L. Schwartz
2005-11-23  8:37       ` Junio C Hamano
2005-11-23 13:56         ` Ryan Anderson
2005-11-23 14:27           ` Perl version support (was Re: [PATCH] git-mv is not able to handle big directories) Randal L. Schwartz
2005-11-23 19:47             ` Perl version support Junio C Hamano
2005-11-23 19:59               ` Randal L. Schwartz [this message]
2005-11-23 21:56             ` Perl version support (was Re: [PATCH] git-mv is not able to handle big directories) H. Peter Anvin
2005-11-23 22:01               ` Randal L. Schwartz
2005-11-23 22:02               ` Morten Welinder
2005-11-28  1:46             ` Ryan Anderson
2005-11-28  8:49               ` Andreas Ericsson
2005-11-23 18:53           ` [PATCH] git-mv is not able to handle big directories Junio C Hamano
2005-11-23 19:54             ` Ryan Anderson
     [not found]         ` <200511231619.41497.lan@ac-sw.com>
2005-11-23 14:29           ` Randal L. Schwartz
2005-11-23  7:26   ` git-mv is not able to handle directory with one file in it Alexander Litvinov
2005-11-23  7:57     ` Andreas Ericsson
2005-11-23  9:57       ` Alexander Litvinov
2005-11-23 10:21       ` Alexander Litvinov
2005-11-23 11:07         ` Josef Weidendorfer
2005-11-23 14:47     ` Josef Weidendorfer

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=86br0bm8yl.fsf@blue.stonehenge.com \
    --to=merlyn@stonehenge.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.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.