git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: git@vger.kernel.org
Subject: Re: [PATCH 1/2] Add expat and expat-devel dependencies (for http-push) to RPM spec.
Date: Sun, 13 Nov 2005 19:40:32 +0100	[thread overview]
Message-ID: <437788A0.6030103@op5.se> (raw)
In-Reply-To: <Pine.LNX.4.64.0511130942490.3263@g5.osdl.org>

Linus Torvalds wrote:
> 
> Quite frankly, I'd really prefer to see the git-core-http as a separate 
> package.
> 

This would get rid of expat and curl dependencies. ssh, rsync and git 
protocols use external programs so they aren't exactly required (from 
the rpm point of view anyways, they'll just fail if rsync or ssh isn't 
installed). I.e. Good idea, but see below.

> I think it's ludicrous that people want to split out gitk (because it 
> wants tcl/tk), but that we then add all of these really obscure 
> dependencies for the http part. 
> 

Couldn't agree more. Moving out the {cvs,arch,svn}-import scripts made 
sense because they were only faintly related to git day-to-day 
operations and forced some really ridiculous dependencies down users 
throats (git requiring subversion was a funny one...).

It *might* make sense to build a very minimalistic package for 
server-side use only, but for client-side use it's really only confusing 
to have a dozen packages to install to get the full functionality.

While we're on the subject of confusing; How about not naming non-core 
packages git-core? It feels wrong to have git-core-http, git-core-cvs 
and git-core-svn since they, strictly speaking, aren't required for core 
operations.

So, to be nicely constructive then I suggest we create the following 
packages;

git-core; Low-level stuff with as few dependencies as possible (ssh and 
openssl should suffice, really). This should be everything needed for 
running a server and should be required by all other git-* packages. It 
will most likely be enough to run most client-side things as well.

git; holds all client side stuff useful for humans interfacing with git 
that introduces "normal" dependencies not necessarily found everywhere 
(gitk and suchlike).

git-email; This one only uses Email::Valid->address(), so I'll import 
that function from the perl module so this dependency can be dropped and 
git-send-email can be in the 'git' package.


Programs introducing obscene or plain weird dependencies (cvsimport, 
svnimport) can be put into their own package, but we should really try 
to keep those extra packages to a minimum and simply force users who 
want all the fluffy niceties of the 'git' package to install whatever's 
required (or install with --nodeps, or from source, or...).

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

  reply	other threads:[~2005-11-13 18:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-13  4:56 [PATCH 1/2] Add expat and expat-devel dependencies (for http-push) to RPM spec Thomas Matysik
2005-11-13 17:46 ` Linus Torvalds
2005-11-13 18:40   ` Andreas Ericsson [this message]
2005-11-13 19:49     ` Linus Torvalds
2005-11-13 20:36       ` Andreas Ericsson
2005-11-13 20:51         ` Linus Torvalds
2005-11-14 17:25           ` David Kågedal
2005-11-14  8:10     ` Junio C Hamano
2005-11-14  8:57       ` Andreas Ericsson
2005-11-14  0:29   ` Thomas Matysik

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=437788A0.6030103@op5.se \
    --to=ae@op5.se \
    --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).