Tom Copeland
1/17/2007 3:47:00 PM
> > Generally, if you have a project called "foo", you'll need
> to name the
> > gem something like "foo-4.2.gem" for it to be deployed on the
> > RubyForge gem index. Of course, you can release a file
> with whatever
> > name you want on your project; this naming limitation only
> applies if
> > you want the gem indexed.
>
>
> Does this mean that you won't be able to release multiple
> gems from the same RubyForge project into the index under an
> umbrella project, like seattlerb does?
Nope, it just means that you won't be able to release a gem who's
spec.full_name is greatly different than the file name.
Yours,
Tom