On Jan 18, 2008 12:09 PM, Junio C Hamano <gitster@pobox.com> wrote:
quoted text
> "Lars Hjemli" <hjemli@gmail.com> writes:
>
> > Hmm, isn't a nonfunctional libgit considered breakage? Without
> > something like this patch it is no longer possible to use
> > write_tar_archive()/write_zip_archive() in libgit.a.
>
> Sorry, but libgit.a is not part of what we deliver.  We do not
> support linking random stuff against libgit.a.  We never did.
> It is not a "library".

I kind of expected this reply, and I know libgit isn't supposed to be
a stable API aginst git internals, but it still feels like a
regression: cgit has been linking against libgit for over a year now
(initial snapshot support added feb 8, 2007), and git-1.5.4 looks like
the first git release which cgit cannot use.

quoted text
> The code movement you did _should_ not hurt so it may be a fine
> material for post 1.5.4, but I haven't carefully compared what
> other change might have accidentally snuck in that patch, and I
> would rather not have to during the rc cycle.

Ok, I can't argue with that.

But could the patch then be part of 1.5.4.X or would I have to wait
for 1.5.5 since it's not considered to fix any breakage in 1.5.4? The
reason I'm asking is that cgit relies on offical git releases (or
rather, the tarballs published on kernel.org when a release is cut),
and it would be a shame if the 1.5.4-series becomes unusable for me
(there's always the possibility to link against a forked git, but I'd
rather not).

-- 
larsh
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html