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

Re: [RFC] Git Perl bindings, and OO interface

From
Jakub Narebski <jnareb@gmail.com>
Date
Nov 30, 2008, 14:50 UTC
Message-ID
<m37i6ljmjy.fsf@localhost.localdomain>
In-Reply-To
<200811301445.18969.nadim@khemir.net>
nadim khemir <nadim@khemir.net> writes:
Show 12 quoted lines
> On Thursday 27 November 2008 02.58.49 Jakub Narebski wrote:
> > ...
> >
> > 7. Git::Refs
> >
> >    It is meant to represent references, mainly branches, and be filled
> >    using git-for-each-ref... and for example used for ref markers.
> >
> > There are probably a few things I have forgot about...
> 
> Thank you for writing the RFC, it's a very good start. I would like to see 
> some strategy for libgit[2] in the RFC. What is your opinion about that?

I do not know enought about libgit2 or even git unofficial internal C API to talk about it.

I did not plan for Perl interface to be actual Perl bindings, using libgit2. Please remember that earlier effort of using XS (Perl <-> C interface) failed because it relied on GCC support for -fPIC and was not sufficiently portable... if I remember it correctly. Calling Git commands and massaging output would be enough for me.

-- 
Jakub Narebski
Poland
ShadeHawk on #git
Previous: nadim khemirNext: Tom Lanyon
Message 3 of 4 in “[RFC] Git Perl bindings, and OO interface”
  1. Jakub NarebskiNov 27, 2008
  2. nadim khemirNov 30, 2008
  3. Jakub NarebskiNov 30, 2008
  4. Tom LanyonJul 10, 2009

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.