[Rubygems-developers] Hoe, Rubyforge, and name confusion
rick.denatale at gmail.com
Thu May 28 15:52:43 EDT 2009
I'm getting nowhere fast.
I'm still getting "invalid package_id" when I try to release.
rubyforge create_package <<my_group_id>> ri_cal
which added a new package number to my autoconfig.yml, but when I try
to release THAT is the new number which comes up as invalid.
I guess I'm going to have to manually upload the gem through the web
I'd sure love to get some advice, it's not that I haven't already been
pulling my hair out with google and reading the code in the hoe and
On Thu, May 28, 2009 at 2:20 PM, Rick DeNatale <rick.denatale at gmail.com> wrote:
> How? I've found the 'documentation' for hoe rather ephemeral.
> On Thu, May 28, 2009 at 2:10 PM, John Barnette <jbarnette at gmail.com> wrote:
>> On May 28, 2009, at 9:10 AM, Rick DeNatale wrote:
>>> 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 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?
>> Hoe allows you to specify the rubyforge_name of a project independently.
>> Have you tried this?
>> ~ j.
>> Rubygems-developers mailing list
>> Rubygems-developers at rubyforge.org
> Rick DeNatale
> Blog: http://talklikeaduck.denhaven2.com/
> Twitter: http://twitter.com/RickDeNatale
> WWR: http://www.workingwithrails.com/person/9021-rick-denatale
> LinkedIn: http://www.linkedin.com/in/rickdenatale
More information about the Rubygems-developers