All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: "Lars Hjemli" <hjemli@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Seth Vidal" <skvidal@fedoraproject.org>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [RFC] cgit in git?
Date: Thu, 11 Dec 2008 14:28:21 -0800 (PST)	[thread overview]
Message-ID: <m3k5a6gxft.fsf@localhost.localdomain> (raw)
In-Reply-To: <8c5c35580812111348iceaf30dyb55183017cff5b1d@mail.gmail.com>

"Lars Hjemli" <hjemli@gmail.com> writes:

> But the buildsystem/policy used by the fedora project does not allow
> network access during package builds, and since it is quite unlikely
> that the git package always will match the exact release needed by the
> cgit package, I only see four options:
> 1) the fedora project makes a 'git-for-cgit' package containing the
> needed release of the git sources
> 2) the cgit release tarballs includes the needed git sources

2b) make cgit .spec use _two_ tarballs as a source, one with cgit
sources, one with git sources.  This assumes that you always use
released git version as a base.

This is immediate solution.

> 3) the cgit sources are subtree-merged into git

I wonder how likely this would be.

> 4) cgit is modified to link against libgit2

Option 4) would be probably best in long term, but libgit2 doesn't
exists yet.

-- 
Jakub Narebski
Poland
ShadeHawk on #git

  parent reply	other threads:[~2008-12-11 22:29 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 [this message]
2008-12-11 22:35 ` Junio C Hamano
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=m3k5a6gxft.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.