[Rubygems-developers] Hoe, Rubyforge, and name confusion
rick.denatale at gmail.com
Thu May 28 12:10:53 EDT 2009
I'm having trouble getting rake release to work. I posted the
following to Dr Nic's forum on newgem, but since it's probably really
a misunderstanding on my part of rubyforge and hoe, I thought I might
get an answer here:
So I'm finally ready to release my gem on rubyforge (It has been
maturing on github for some weeks).
When I tried to rake release, I first ran into the issue of having to
specify the version as an environment variable, then I ran into the
"no <package_id> configured for <rical>
Googling around for an answer, it seemed that I'd originally messed up
in naming the ruby forge project rical when the gem name is ri_cal.
So not finding a way to rename a project I created another one. But
I'm still running into the same issues.
I did the rubyforge config incantations but when I rake release
$rake release VERSION=0.5.0
..... lots of output
Successfully built RubyGem
mv ri_cal-0.5.0.gem pkg/ri_cal-0.5.0.gem
Releasing ri_cal v. 0.5.0
no <package_id> configured for <ri_cal>
$ cat ~/.rubyforge/auto-config.yml
ri_cal (master)⚡ $
So now it seems that the problem is that there's a discrepency between
ri_cal, and ri-cal which is the 'unix name' of the project and which
according to the rubyforge instruction can't contain an underscore but
can contain a dash.
So how do I straighten this mess out?
More information about the Rubygems-developers