Update Sept 30 2009: This has been replaced with the display of the gem namespaces in the normal GForge user interface.
Prompted by a support request - here's a dump of the current gem namespace ownership in the RubyForge gem index. If folks find this useful, let me know and set this up to be regenerated via a daily cronjob.
Nice Tom. I would suggest to only include the basename, however. So, instead of this:
The gem 'win32-api-1.2.2-x86-mswin32-60.gem' is owned by the project 'win32utils'
The gem 'win32-api-1.3.0-x86-mswin32-60.gem' is owned by the project 'win32utils'
You show this:
The gem 'win32-api' is owned by the project 'win32utils'.
What do you think?
Dan
Posted by: Daniel Berger | January 04, 2009 at 05:32 PM
@dan, yup, that would be better... just some munging to make that list shorter...
Posted by: tomcopeland | January 04, 2009 at 05:37 PM
@dan, hm, I've been fiddling with inject for a bit, and the tricky part is telling where the gem 'name' stops... for example, in "win32-api-1.3.0-x86-mswin32-60.gem", is the gem name "win32" or "win32-api"? I could load up all the gem specs, I guess... that would give me the real name. Lots of I/O there, though. Right now I was just reading the cached name to project map that the RubyForge gem indexer creates to prevent namespace clashes.
Posted by: tomcopeland | January 04, 2009 at 06:41 PM
I think the majority of them could be parsed out with this regex: string[/(.*?)\-\d+\./, 1]. Basically, look for everything up to a hyphen + number + dot.
Posted by: Daniel Berger | January 04, 2009 at 08:13 PM
@dan, good one, done and previous list overwritten. That's a much more readable list for sure, thanks!
Posted by: tomcopeland | January 04, 2009 at 08:31 PM
Only 4053 gems? Seems low. But then some people don't publish gems (only source files) and others push their gems on github.
Posted by: DJB | January 05, 2009 at 09:08 AM
@dan, yeah, 4053 unique gems... interesting ratio given that there are 13000+ projects. Of course, some projects never get off the ground, and as you said, others push to github or are Rails plugins or non-gems or whatever.
Posted by: tomcopeland | January 05, 2009 at 09:10 AM
This is useful. I'm surprised there's no programmatic way to know who publishes which gem. This is a good alternative.
-=r
Posted by: roger | January 23, 2009 at 07:24 PM
Hello Tom. First time emailer 2 u.
I have deployed RoR on Ubuntu 8.10 using instructions https://help.ubuntu.com/community/RubyOnRails#Installing%20RubyGems
When I do a 'rake:db:fixtures:load' i get the following error msg:
Could not find RubyGem rubyforge (>= 1.0.3)
(Note: Prior to getting the above error msg, i had gotten a similar error msg, about 'not finding RubyGem hoe'. So I did a 'gem install hoe' and the error msg went away).
So it seems i can do a 'gem install rubyforge' and hope the error go away.
Question: Rather than getting these error msgs one step at a time and installing the missing stuff, do u know if there is something that I did NOT install that would had prevented these error msgs?
Thx in advance for responding to my comment.
DT
Posted by: DT | April 08, 2009 at 02:58 PM
@dt - yup, if the Rails app was writing using "config.gems" settings you can install all the dependent gems using "rake gems:install".
Posted by: tomcopeland | April 08, 2009 at 03:06 PM
Thx Tom. I'll give it a try.
Danesh
Posted by: DT | April 08, 2009 at 03:59 PM