Re: git 0.99.9: Subversion importer breaks RPM generation (rpmbuild bug)

On Mon, 31 Oct 2005, H. Peter Anvin wrote:

The git-core RPM definitiely needs to be split.  Doubly ironic that it's
called "core".

I don't think it's necessarily ironic. It's actually a good thing.

I think that what we want to have is one _project_ (called "git"), which 
can generate multiple RPM's ("git-core", "git-svnimport", "git-docs", 
whatever).

So I think it was good that we called the RPM "git-core". We've just not 
yet done the obvious thing to create a few _other_ RPM's.

Now, I'm not certain how happy RPM would be with having one source RPM 
generate multiple binary RPM's, so we might have problems with some stupid 
RPM rules, but I think we should really do this. There's always going to 
be some extra feature that not everybody needs, but that it would be silly 
to have its own project for. 

Having one bigger project means that it's much easier to maintain, and 
there's less administrative overhead (good maintainers are really hard to 
find: you should realize how lucky we are to have Junio). Trying to split 
up the source code into independent projects at this level would just be 
much more pain than it's worth. But clearly we want to split up the RPM's.

		Linus