Re: Problems using perl's Git.pm module

From: demerphq <demerphq@gmail.com>
Date: Dec 2, 2010, 18:41 UTC
Message-ID: <AANLkTimKKssBbtuLKCqG9WGbOe+-CH4pc5PDaNxCH_PS@mail.gmail.com>
In-Reply-To: <20101202181425.GG3962@burratino>

On 2 December 2010 19:14, Jonathan Nieder <jrnieder@gmail.com> wrote:

Show 15 quoted lines

> demerphq wrote:
>> On 2 December 2010 18:46, Junio C Hamano <gitster@pobox.com> wrote:
>> > Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
>>>> Why are you using it? It's for internal use only.
>>>
>>> That is not a valid question nor answer, I am afraid.
>>
>> So you are saying that it is for more than internal use?
>
> I assume so.  I had guessed the same thing (that it is meant to be
> generally useful), based on the following:
>
>  - it is installed to be usable with a simple "use Git"
>   automatically

Well that is true. But im not sure that is a good reason.

>  - "perldoc Git" tells me that this module gives Perl scripts an easy
>   way to interface the Git version control system, not that it is an
>   implementation artifact

Any perl module, or script, or podfile installed in a place that perldoc knows about is available to perldoc.

>  - tools like "git svn" were not historically part of core git, and
>   usage by them was not exactly internal use.

Well, the counter  arguments are:

No back-compat layer for older gits. Tight binding to a particular git
- no availability of upgrades independent of upgrading git. No
availability or review of the module on the standard venues for doing
so for Perl modules. CPAN, CPANTESTERS, smoke reports, etc.

And well the line:

# Totally unstable API. $VERSION = '0.01';

STRONGLY suggests that the module should not be used by code outside the Git package itself.

Cheers, yves

-- 
perl -Mre=debug -e "/just|another|perl|hacker/"