Re: Problems using perl's Git.pm module
- From
- Josef Wolf <jw@raven.inka.de>
- Date
- Dec 3, 2010, 08:38 UTC
- Message-ID
- <20101203083827.GD26070@raven.wolf.lan>
- In-Reply-To
- <AANLkTimKKssBbtuLKCqG9WGbOe+-CH4pc5PDaNxCH_PS@mail.gmail.com>
On Thu, Dec 02, 2010 at 07:41:00PM +0100, demerphq wrote:
> 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.
I don't understand this one. Why do you need independent upgrades here? Since Git.pm comes with git core, the installed version of Git.pm should always match the installed version of git.
> No > availability or review of the module on the standard venues for doing > so for Perl modules. CPAN, CPANTESTERS, smoke reports, etc.
A module on CPAN has better tests for perl integration. A module in git-core has better tests for git integration.
You trade one for the other. The question is which is more critical. IMHO, git-integration is more critical.