# Re: gitweb.cgi in C

3 messages from 2005-12-09 to 2005-12-09. Participants: Mark Allen, Randal L. Schwartz, Junio C Hamano.
Thread: https://gitlist.dev/t/2790

## Mark Allen, 2005-12-09 15:28

Subject: Re: gitweb.cgi in C
Message-ID: <20051209152847.28358.qmail@web34310.mail.mud.yahoo.com>
URL: https://gitlist.dev/e/20051209152847.28358.qmail%40web34310.mail.mud.yahoo.com

```
Randal L. Schwartz wrote:
>>>>> "Junio" == Junio C Hamano <junkio@cox.net> writes:
Junio> Yes, that is exactly what I meant by what Smurf is working on -- 
Junio> libified git with Pyrex.

> Pyrex?  not XS?  I'd like to see Perl "use Git;". :)

I have a lot of interest in writing an XS interface for GIT but I've been waiting for 1.0
to officially release so I can be assured of a somewhat stable interface target.

I started working on a GIT-XS project around GIT 0.9 timeframe, but the changes to APIs
and calls was still way too rapid, so I decided to back burner it. 

I haven't looked at the libification work that Smurf is doing (haven't made time for it
lately), but if it's not TOO python specific, maybe I can use it too.

Cheers,
--Mark

```

## Randal L. Schwartz, 2005-12-09 15:45

Subject: Re: gitweb.cgi in C
Message-ID: <86r78m8ea2.fsf@blue.stonehenge.com>
URL: https://gitlist.dev/e/86r78m8ea2.fsf%40blue.stonehenge.com
In-Reply-To: <20051209152847.28358.qmail@web34310.mail.mud.yahoo.com>

```
>>>>> "Mark" == Mark Allen <mrallen1@yahoo.com> writes:

Mark> I started working on a GIT-XS project around GIT 0.9 timeframe, but the changes to APIs
Mark> and calls was still way too rapid, so I decided to back burner it. 

Mark> I haven't looked at the libification work that Smurf is doing (haven't made time for it
Mark> lately), but if it's not TOO python specific, maybe I can use it too.

A "lite" version using Inline::C can be quickly constructed if
only the API were all listed in one place, or a few easy to find places.

I spent about ten minutes trying to find this information a few weeks
back, but apparently, that was about five minutes (or more) too short.

Any quick pointers on how -lgit is constructed?

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

```

## Junio C Hamano, 2005-12-09 17:59

Subject: Re: gitweb.cgi in C
Message-ID: <7vhd9i40dx.fsf@assigned-by-dhcp.cox.net>
URL: https://gitlist.dev/e/7vhd9i40dx.fsf%40assigned-by-dhcp.cox.net
In-Reply-To: <86r78m8ea2.fsf@blue.stonehenge.com>

```
merlyn@stonehenge.com (Randal L. Schwartz) writes:

>>>>>> "Mark" == Mark Allen <mrallen1@yahoo.com> writes:

> Mark> I haven't looked at the libification work that Smurf is
> Mark> doing (haven't made time for it lately), but if it's not
> Mark> TOO python specific, maybe I can use it too.

> A "lite" version using Inline::C can be quickly constructed if
> only the API were all listed in one place, or a few easy to find places.

Guys, the "libificiation work" is more than that, and the more
important and bigger task is not the part you connect libgit to
your favorite P* languages, but first the part to reorganize
libgit to be usable in that form.

I've outlined what needs to be done a couple of months ago:

	http://marc.theaimsgroup.com/?t=112687447700001

```
