Re: [PATCH/RFC] Build a shared / renamed / "stable" version of the library?
- From
Matthias Urlichs <smurf@smurf.noris.de>
- Date
- Sep 16, 2005, 21:10 UTC
- Message-ID
- <20050916211040.GU7646@kiste.smurf.noris.de>
- In-Reply-To
- <7vmzmcj1eo.fsf@assigned-by-dhcp.cox.net>
Hi,
Junio C Hamano:
> Matthias, I think you are solving a wrong problem. More > precisely, solving problems in a wrong order. >
I've since looked a bit more closely at the "library" code, and ... well, you're obviously right. :-/
> can read many blobs without spawning git-cat-file for each of > them, but that is about how far you could go.
Precisely that was the first application I needed the library for. ;-)
Show 8 quoted lines
> Don't get me wrong. I would really want to see the guts of git > libified and SWIG'ed. That would help not just your Python > thing but also StGIT and Fredrik merge (both are Python), as > well as gitk (tcl/tk) and gitweb (Perl). I would not even mind > seeing all the git barebone Porcelain redone in Python once we > go in that direction, ditching the shell scripts we currently > have. >
You and me both...
> *5* Maybe we would want separate git_init_cache, > git_init_objects, ... and be able to mix and match them. Maybe > not. >
Makes sense. First steps would probably be to invent "struct git_repository" and "struct git_cache" data structures. Fun. ;-)
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
INSIDE, I have the same personality disorder as LUCY RICARDO!!
-- Zippy the Pinhead