Re: [ANNOUNCE] GIT 0.99.9g

Andreas Ericsson [off-list ref] writes:

Jim Radford wrote:

quoted

On Thu, Nov 10, 2005 at 12:14:29AM -0800, Junio C Hamano wrote:

quoted

  I think archimport part needs to be split out just like its
  svn/cvs cousins,

I don't agree...

How is this different for when svnimport and cvsimport was moved out?..

quoted

The main reason I see for splitting cvs and email import out is the
non-standard dependencies, cvsps and perl(Email::Valid).

Define "non-standard". String::ShellQuote isn't installed by default on 
Fedora Core 3 but is required by git-archimport.

I am with Andreas here.

If you are using git to manage development in a tightly knitted
group (e.g. company internal project) and are unlikely to be
exchanging email patches, not having to pull Email::Valid into
your system is a good thing, because you would not be using
git-mail.  If you are not dealing with development history
stored in svn or tla, not having to install git-svn nor git-tla
is a good thing.

Technical reasons like package availablity and required package
size count, but I do not think we should be doing the split
purely for technical reasons.  The split should aim primarily
to give convenience for the users.

That reminds me, Andreas, you said something about feeding me
spec updates last week but Jim beated you.  I am open to
improvements from both of you.  Obviously the invitation is not
limited to two of you ;-).

On Thu, Nov 10, 2005 at 12:48:15PM -0800, Junio C Hamano wrote:

Andreas Ericsson [off-list ref] writes:

quoted

Jim Radford wrote:

quoted

quoted

The main reason I see for splitting cvs and email import out is the
non-standard dependencies, cvsps and perl(Email::Valid).

quoted

Define "non-standard". String::ShellQuote isn't installed by default on 
Fedora Core 3 but is required by git-archimport.

You are right.  I had missed that it required String::ShellQuote.  It
should go in it's own RPM (and it already has).

-Jim