[Rubygems-developers] MetaProject

Hugh Sasse hgs at dmu.ac.uk
Fri Sep 2 16:08:44 EDT 2005


On Fri, 2 Sep 2005, Chad Fowler wrote:

>
> On 01-Sep-05, at 8:55 PM, aslak hellesoy wrote:

I managed to miss that.

>
>> Hi all,
>> 
>> The past month I've been working on a project (MetaProject:
>> http://xforge.rubyforge.org/) that among other things includes a quick
>> release system (QRS) for (among other places) RubyForge.
>> 
>> With MetaProject's Rake task, releasing new gems on RubyForge is a breeze:

I like the irony!  QRS means "send more slowly" :-)
http://hharc.sa.utoronto.ca/q-codes.php

>> 
>> task :release_files => [:gem] do
>>  release_files = FileList[
>>    "pkg/#{PKG_FILE_NAME}.gem"
>>  ]
>>
>>  Rake::XForge::Release.new(MetaProject::Project::XForge::RubyForge.new('xforge'))
>> do |release|
>>    # Never hardcode user name and password in the Rakefile!
>>
>>    release.user_name = ENV['RUBYFORGE_USER']
>>
>>    release.password = ENV['RUBYFORGE_PASSWORD']

Umm, you probably shouldn't leave them in the ENVIRONMENT either,
because it can be picked up with the PS command.

>>    release.files = release_files.to_a
>>    release.release_name = "MetaProject #{PKG_VERSION}"
>>
>>    # The rest of the options are defaults (among others,
>> release_notes and release_changes, parsed from CHANGES)
>>  end
>> end

Nice.

>> 
>> Would you consider mentioning this in the RubyGems documentation?
>> 
>> 
>

         Hugh


More information about the Rubygems-developers mailing list