Git Hub Serves More Ruby Gems Than Rubyforge
11–20 of 20 posts
Re: Git Hub Serves More Ruby Gems Than Rubyforge
#12Github server gem as authorname-projectname so duplicate of same project should be removed from this counting. That will give actual number
Gem publishing is opt-in. Even for forks.
Re: Git Hub Serves More Ruby Gems Than Rubyforge
#13Earlier quoted context omitted.
We were talking tonight about CPAN modules, Python eggs, and PEAR... pears? We'd love to take what we've learned serving Rubygems and apply the knowledge to any other languages that have a solid packaging system.
Python may be a bit more difficult than you'd expect. The tools -- easy_install, pip, etc. -- are built around a core which, though it can use alternate sources to look for packages, happens to have things like heuristics for screen-scraping pypi.python.org hard-coded in.
Re: Git Hub Serves More Ruby Gems Than Rubyforge
#14GitHub soon will be the new operating system for coders: repository, product wiki, tech blog, issue tracker, collaboration, messaging
Re: Git Hub Serves More Ruby Gems Than Rubyforge
#15When will Github do the same thing for CPAN modules? I would love to not have to release modules, and instead just tag my project as stable and let the toolchain do its thing. An API for this would also be acceptable; then I can implement this for them.
We were talking tonight about CPAN modules, Python eggs, and PEAR... pears? We'd love to take what we've learned serving Rubygems and apply the knowledge to any other languages that have a solid packaging system.
We (the ServerJS pseudo working group: https://wiki.mozilla.org/ServerJS) are currently looking at package management solutions for server-side JavaScript.
Using Rubygems with other languages like JS is one possibility, then we would get the Github integration for free.
And there's JSAN (http://openjsan.org/).
Kris Kowal hacked together one that pulls zipped repos directly from GitHub (or potentially any HTTP server) (tentatively named "tusk", implemented on "narwhal": http://github.com/tlrobinson/narwhal/tree/integration). One neat thing about that is you can create new versions just by tagging.
Re: Git Hub Serves More Ruby Gems Than Rubyforge
#16Github server gem as authorname-projectname so duplicate of same project should be removed from this counting. That will give actual number
18 webrat
18 will_paginate
20 god
29 rack
30 sinatra
31 twitter
33 integrity
37 merb
48 dm
71 ruby
gem list -r -s http://gems.github.com | cut -d- -f 2 | cut -d " " -f 1 | sort | uniq -c | sort -n | tail -10Re: Git Hub Serves More Ruby Gems Than Rubyforge
#17Earlier quoted context omitted.
We were talking tonight about CPAN modules, Python eggs, and PEAR... pears? We'd love to take what we've learned serving Rubygems and apply the knowledge to any other languages that have a solid packaging system.
Python may be a bit more difficult than you'd expect. The tools -- easy_install, pip, etc. -- are built around a core which, though it can use alternate sources to look for packages, happens to have things like heuristics for screen-scraping pypi.python.org hard-coded in.
Re: Git Hub Serves More Ruby Gems Than Rubyforge
#18Earlier quoted context omitted.
Python may be a bit more difficult than you'd expect. The tools -- easy_install, pip, etc. -- are built around a core which, though it can use alternate sources to look for packages, happens to have things like heuristics for screen-scraping pypi.python.org hard-coded in.
Does anyone else find the idea of a package installer that /screen scrapes a website for download links/ deeply and fundamentally disturbing, or is it just me?
Re: Git Hub Serves More Ruby Gems Than Rubyforge
#19It's not really accurate, though because this lists every user's fork of a gem as a distinct gem. Here's a script I put together to get a different count, which I believe is more of a "real" count.
It's 3140 as I write this, not 4766.
Re: Git Hub Serves More Ruby Gems Than Rubyforge
#20This is something to be proud of, and github is great work. It's not really accurate, though because this lists every user's fork of a gem as a distinct gem. Here's a script I put together to get a different count, which I believe is more of a "real" count. http://gist.github.com/120207 It's 3140 as I write this, not 4766.