From: Junio C Hamano <gitster@pobox.com>
To: "Lars Hjemli" <hjemli@gmail.com>
Cc: "Seth Vidal" <skvidal@fedoraproject.org>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [RFC] cgit in git?
Date: Thu, 11 Dec 2008 14:35:34 -0800 [thread overview]
Message-ID: <7vwse6bart.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <8c5c35580812111348iceaf30dyb55183017cff5b1d@mail.gmail.com> (Lars Hjemli's message of "Thu, 11 Dec 2008 22:48:45 +0100")
"Lars Hjemli" <hjemli@gmail.com> writes:
> 2) the cgit release tarballs includes the needed git sources
>
> Option 2 is doable but still requires the fedora project to support
> two git packages (but now the 'git-for-cgit' package is hidden inside
> the cgit source tree). The good thing about this option is that it
> only requires some minor modifications to the cgit releases.
I do not understand why this is any extra work for fedora. Instead of
running "make get-git" and then running your build procedure, they need to
just run your build procedure because you now ship your source with the
matching version of the git source, which sounds like the right thing to
me. You do not install anything from the contained git.git area (we do
not do shared objects, nor public header files) to the end product, right?
Doesn't cgit bind git.git as a subproject at the source level? I would
expect that the most natural release tarball for such a project would be a
single tarball that has both the superproject itself _and_ the submodules
it contains already extracted, iow, the state of your tree after you run
"make get-git".
next prev parent reply other threads:[~2008-12-11 22:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 21:48 [RFC] cgit in git? Lars Hjemli
2008-12-11 22:15 ` Miklos Vajna
2008-12-11 22:28 ` Jakub Narebski
2008-12-11 22:35 ` Junio C Hamano [this message]
2008-12-11 23:37 ` Lars Hjemli
2008-12-12 0:15 ` Todd Zullinger
2008-12-11 22:40 ` Johan Herland
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=7vwse6bart.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=hjemli@gmail.com \
--cc=skvidal@fedoraproject.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).