Re:Git Hub Serves More Ruby Gems Than Rubyforge
by mhartl on Friday May 29, 2009 @01:02AM
(#631570)
Every time I go to RubyForge to make a gem, I always get stuck on the first page, where they make you name the project, fill out the project purpose and summary, and so on. Then I realize I'm not ready to make it a gem yet, and push the repo up to GitHub.
Re:Git Hub Serves More Ruby Gems Than Rubyforge
by jrockway on Friday May 29, 2009 @12:27AM
(#631533)
When 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.
Re:Git Hub Serves More Ruby Gems Than Rubyforge
by jrockway on Friday May 29, 2009 @02:28AM
(#631639)
Excellent. Please send me an email (jon AT jrock.us) and I can give you more detail (and help you implement).
Basically, CPAN modules are just archives (usually tar.gz). There is a program called the "PAUSE indexer" that examines the archives, and generates a mapping of module name => archive file. The CPAN client fetches this file, and then knows what archive to download to install the named module.
All github would need to do is maintain this index file; the rest is handled client-side.
Re:Git Hub Serves More Ruby Gems Than Rubyforge
by tlrobinson on Friday May 29, 2009 @06:16AM
(#631825)
I wish there was a standard package management protocol. Why does every language have to reinvent package management? They could still write the package manager clients (and servers) in their language, as they all seem to love to do.
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.
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
by ubernostrum on Friday May 29, 2009 @02:48AM
(#631668)
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
by simonw on Friday May 29, 2009 @06:40AM
(#631838)
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
by ben on Friday May 29, 2009 @05:05PM
(#632811)
This 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.
Re:Git Hub Serves More Ruby Gems Than Rubyforge
by pjhyett on Friday May 29, 2009 @07:56PM
(#633061)
Forks aren't gem-enabled by default. Meaning, the forker had to go out of their way to indicate there is something different about their gem. Is it possible there isn't unique code on some of these gems? Sure, but I wouldn't discount them outright.
GitHub soon will be the new operating system for coders: repository, product wiki, tech blog, issue tracker, collaboration, messaging
Thanks, guys, for making sharing code so easy!
An API for this would also be acceptable; then I can implement this for them.
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.
Basically, CPAN modules are just archives (usually tar.gz). There is a program called the "PAUSE indexer" that examines the archives, and generates a mapping of module name => archive file. The CPAN client fetches this file, and then knows what archive to download to install the named module.
All github would need to do is maintain this index file; the rest is handled client-side.
(The indexing algorithm isn't much more than this: http://github.com/jrockway/metacpan/blob/be78711a6f12afd3b71...)
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.
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.
Gem publishing is opt-in. Even for forks.