From: Josef Wolf <jw@raven.inka.de>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Problems using perl's Git.pm module
Date: Fri, 3 Dec 2010 09:27:01 +0100 [thread overview]
Message-ID: <20101203082701.GC26070@raven.wolf.lan> (raw)
In-Reply-To: <AANLkTi=8=k9iNWzTnGz821k9A_CZNiEt_KkC8TXu6oS_@mail.gmail.com>
On Thu, Dec 02, 2010 at 02:23:32PM +0100, Ævar Arnfjörð Bjarmason wrote:
> On Thu, Dec 2, 2010 at 12:40, Josef Wolf <jw@raven.inka.de> wrote:
> > I am trying to use perl's Git.pm module, but for some reason, it keeps
> > bailing out:
> Why are you using it?
1. It is always available whenever git is available, so I don't need to
search/install additional packages just to hack some scripts. If you
have to support multiple distros/OS'es, it starts getting a PITA to
find out what/how to install those additional packages.
2. Since it is used by the core developers, I assumed that it would be
more robust than some third-party wrappers.
3. Since it is bundled with git, I'd not expect any version mismatches.
With a third-party wrapper, version mismatches are much more likely.
> Couldn't you use one of the Perl Git wrappers on the CPAN?
Which one would you suggest?
next prev parent reply other threads:[~2010-12-03 8:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 11:40 Problems using perl's Git.pm module Josef Wolf
2010-12-02 13:23 ` Ævar Arnfjörð Bjarmason
2010-12-02 16:19 ` Jonathan Nieder
2010-12-02 17:30 ` Ævar Arnfjörð Bjarmason
2010-12-02 17:46 ` Junio C Hamano
2010-12-02 18:10 ` demerphq
2010-12-02 18:14 ` Jonathan Nieder
2010-12-02 18:41 ` demerphq
2010-12-02 19:05 ` [RFC/PATCH] Git.pm: discourage casual use Jonathan Nieder
2010-12-02 19:30 ` Junio C Hamano
2010-12-02 19:45 ` Jonathan Nieder
2010-12-03 8:38 ` Problems using perl's Git.pm module Josef Wolf
2010-12-03 9:02 ` demerphq
2010-12-02 18:18 ` Junio C Hamano
2010-12-02 18:32 ` demerphq
2010-12-03 8:27 ` Josef Wolf [this message]
2010-12-03 9:10 ` Jonathan Nieder
2010-12-02 17:51 ` Junio C Hamano
2010-12-03 8:14 ` Josef Wolf
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=20101203082701.GC26070@raven.wolf.lan \
--to=jw@raven.inka.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
/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).