[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

rubygems/rubyforge question - release, package, group?

Rob Sanheim

12/5/2007 3:26:00 PM

Hi

Could someone please explain the difference between a release, a
package, and a group when releasing gems to rubyforge (via
rubyforge/hoe)?

What is the convention for a gem in rubyforge when its the 'only'
thing in that project?

thanks,
Rob

http://robs...
http://thinkrel...
2 Answers

Giles Bowkett

12/5/2007 4:18:00 PM

0

> Could someone please explain the difference between a release, a
> package, and a group when releasing gems to rubyforge (via
> rubyforge/hoe)?
>
> What is the convention for a gem in rubyforge when its the 'only'
> thing in that project?

My hackariffic guesstimate is, I just released the gem file and that
was that. But then again this was just a test release, to see if I
could get the release process working, and I only used Hoe for setting
up the initial dirs etc.

--
Giles Bowkett

Podcast: http://hollywoodgrit.bl...
Blog: http://gilesbowkett.bl...
Portfolio: http://www.gilesg...
Tumblelog: http://giles....

Ben Bleything

12/5/2007 4:36:00 PM

0

On Thu, Dec 06, 2007, Rob Sanheim wrote:
> Could someone please explain the difference between a release, a
> package, and a group when releasing gems to rubyforge (via
> rubyforge/hoe)?

IIRC, and I'm sure someone will correct me if I'm wrong:

* group: the project name
* package: the "subproject" in that group
* release: the actual release that the files go into

This is best illustrated with an example:

http://rubyforge.org/proj...

The group is "laika", and there are two packages, athenaeum and linen.
If you click the download link for Linen, you'll see that there are a
number of releases, each of which has 3 files.

> What is the convention for a gem in rubyforge when its the 'only'
> thing in that project?

Call the package the same as the group.

Ben