Gems

[Justin Love]

So far at RubyConf I've talked to the developer of Fog, who was
hesitant to break the project up in gems, and Yehuda Katz, who said
Rails was one repository with several gems. I talked with Michael
about this a bit and it's still under consideration.

There was a Thurs. night lighting talks about gem naming that
basically said use underscore - dashes are for variations (like a
person's fork)

http://segment7.net/projects/ruby/RubyConf/2010/How%20to%20Name%20Gems.pdf

--
Justin Love -- http://JustinLove.name/
http://ComputerGeneratedDreams.com/
"[T]he woods would be silent if no bird sang except the best."
 - Henry Van Dyke

[Michael Edgar]

I'm checking out the rails repo right now, and they do have that structure.

However, it seems that their gemspecs are manually managed, whereas

right now we're using Jeweler to integrate with git. That handles a lot of

the heavy lifting.

I've created https://github.com/michaeledgar/amp_complete/ to see if the

one repo approach works as an experiment. I'm sure it will, of course, it's

just a matter of finding the best workflow. Keeping in mind that gems are

released infrequently but development happens a lot, I think I'd even prefer

manually updating gemspecs to the current approach.