From: Juliusz Chroboczek <Juliusz.Chroboczek@pps.jussieu.fr>
To: darcs-devel@darcs.net
Cc: git@vger.kernel.org
Subject: Darcs-Git: upgrading to Git 0.99
Date: Sat, 16 Jul 2005 22:45:47 +0200 [thread overview]
Message-ID: <7islyev5s4.fsf@lanthane.pps.jussieu.fr> (raw)
[CC'd to the Git mailling list; please CC any replies to Darcs-Devel]
David, Ian,
I'd like to upgrade the Git code used in Darcs to 0.99 (we're
currently using 0.6). There are two good reasons for that, the first
of which is actually a showstopper:
- the format of Git repositories has changed incompatibly, with a new
kind of thing called the ``pack'' (a very neat performance hack, by
the way); hence, Darcs-Git is unable to read recent Git repos,
unless you use the Git tools to unpack them;
- 0.99 actually exports usable interfaces, which will allow us to use
pristine Git sources in Darcs.
Now I'm wondering how to do that. Currently, I'm using a nasty hack
using the C preprocessor to include just the sources we need in
Darcs. As 0.99 builds a ``libgit.a'', I'd like to use that instead.
There are three ways to do that:
(1) require that the users put a suitable libgit.a in /usr/local/lib
before building Darcs, and distribute a tarball of Git from
darcs.net;
(2) include just the sources needed for libgit.a in Darcs, and have
the Darcs build build a local libgit
(3) as (2), but include all of Git, including their
``user-friendly'' scripts.
Solution (2) will include 33 files totalling 167KB, while (3) is about
a megabyte of source.
My personal favourite is solution (2), as it is simple for both the
users and us. I'm not very keen on (1), as it will cause problems
when the friendly Git folks change their interfaces, but have no
strong dislike towards it if it's what you think is right. (3) is
definitely overkill.
Juliusz
next reply other threads:[~2005-07-16 20:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-16 20:45 Juliusz Chroboczek [this message]
2005-07-17 10:40 ` [darcs-devel] Darcs-Git: upgrading to Git 0.99 David Roundy
2005-07-18 4:46 ` git, porcelain, darcs, and version 1.0 Bryan Larsen
2005-07-18 19:11 ` Junio C Hamano
2005-07-18 20:18 ` Bryan Larsen
2005-07-18 19:49 ` Juliusz Chroboczek
2005-07-18 20:28 ` Bryan Larsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7islyev5s4.fsf@lanthane.pps.jussieu.fr \
--to=juliusz.chroboczek@pps.jussieu.fr \
--cc=darcs-devel@darcs.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).