using git for projects with multiple gems on rubyforge

[Joel VanderWerf]

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...

[1] google "git branch subproject"

[2] http://drnicwilliams.com/2008/04/08/git-for-rubyforge-accounts/ --
Dr. Nic suggests using branches for subprojects, but it sounds like an
abstract thought, and not something he has tried.

[3] http://git.or.cz/gitwiki/SubprojectSupport

[4] http://book.git-scm.com/5_submodules.html

 

[Jeremy Hinegardner]

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/

 

[Joel VanderWerf]

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.

That's probably what I'll do for now

Still, I filed a feature request on rubyforge for multiple git repos.
Here's the url, in case anyone wants to comment there.[1]

[1]
http://rubyforge.org/tracker/index.php?func=detail&aid=26861&group_id=5&atid=104