git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Problems using perl's Git.pm module

From
JWJosef Wolf <jw@raven.inka.de>
Date
Dec 3, 2010, 08:27 UTC
Message-ID
<20101203082701.GC26070@raven.wolf.lan>
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?
Previous: demerphqNext: Jonathan Nieder
Message 16 of 19 in “Problems using perl's Git.pm module”
  1. Josef WolfDec 2, 2010
  2. Ævar Arnfjörð BjarmasonDec 2, 2010
  3. Jonathan NiederDec 2, 2010
  4. Ævar Arnfjörð BjarmasonDec 2, 2010
  5. Junio C HamanoDec 2, 2010
  6. demerphqDec 2, 2010
  7. Jonathan NiederDec 2, 2010
  8. demerphqDec 2, 2010
  9. Git.pm: discourage casual useJonathan Nieder, Dec 2, 2010
  10. Junio C HamanoDec 2, 2010
  11. Jonathan NiederDec 2, 2010
  12. Josef WolfDec 3, 2010
  13. demerphqDec 3, 2010
  14. Junio C HamanoDec 2, 2010
  15. demerphqDec 2, 2010
  16. Josef WolfDec 3, 2010
  17. Jonathan NiederDec 3, 2010
  18. Junio C HamanoDec 2, 2010
  19. Josef WolfDec 3, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.