From: Jeremy Hinegardner <jeremy@...>
Date: 2009-08-02T10:45:24+09:00
Subject: Re: using git for projects with multiple gems on rubyforge

On Sun, Aug 02, 2009 at 01:55:25AM +0900, Joel VanderWerf wrote:
>
> Some rubyforge projects release more than one sequence of gems.
>
> Has anyone found a way to manage the source for multiple gems in the unique 
> git repository for the project? Is it better to use github, with a separate 
> repos for each gem? Or just create an extra rubyforge project for each 
> subproject (which seems too heavyweight for small gems)?
>
> Is there any chance that rubyforge could support several git repos per 
> project?
>
> There are some ideas[1,2] floating around for using git branches for 
> subprojects, but that adds a layer of complexity and 
> off-the-beaten-trackness that makes me uncomfortable. And the official word 
> is not encouraging[3].
>
> It doesn't look like git submodule is the answer[4]... you still need a 
> repos for the submodule. (Maybe that argues for using github.)
>
> Any ideas appreciated...

I think I started using github before rubyforge offered git repos, so that's
where I've been the whole time.  My main rubyforge project, copiousfreetime[1],
uses 1 github repo per project.  I manage the publishing of docs, gems, packages
and such with rake tasks.

enjoy,

-jeremy

[1] http://rubyforge.org/projects/copiousfreetime/

-- 
========================================================================
 Jeremy Hinegardner                              jeremy@hinegardner.org