Comments on: Creating and Distributing your own gem: a quick rundown http://www.pathf.com/blogs/2009/01/creating-and-distributing-your-own-gem-a-quick-rundown/ Running commentary about agile development, user experience design and Ajax. Fri, 05 Mar 2010 19:33:43 -0600 http://wordpress.org/?v=2.8.4 hourly 1 By: Akhil Bansal http://www.pathf.com/blogs/2009/01/creating-and-distributing-your-own-gem-a-quick-rundown/comment-page-1/#comment-5606 Akhil Bansal Wed, 14 Jan 2009 18:56:23 +0000 http://www.pathf.com/blogs/?p=1357#comment-5606 Good article, Thanks Good article, Thanks

]]> By: Sharad Jain http://www.pathf.com/blogs/2009/01/creating-and-distributing-your-own-gem-a-quick-rundown/comment-page-1/#comment-5594 Sharad Jain Wed, 14 Jan 2009 04:41:11 +0000 http://www.pathf.com/blogs/?p=1357#comment-5594 Patrick, thanks for stopping by. Correct, there are a few quirks with both, newgem and hoe. I also don't like that they create a runtime dependency on themselves eventhough generated gem do not need them. Do they? I hope, your gem doesn't create a dependency on itself ;-) And, I also like the github task that you provided. Will try it out. Thanks. Patrick, thanks for stopping by. Correct, there are a few quirks with both, newgem and hoe. I also don’t like that they create a runtime dependency on themselves eventhough generated gem do not need them. Do they? I hope, your gem doesn’t create a dependency on itself ;-) And, I also like the github task that you provided. Will try it out. Thanks.

]]> By: Ennuyer.net » Blog Archive » 2009-01-13 - Today’s Ruby/Rails Reading http://www.pathf.com/blogs/2009/01/creating-and-distributing-your-own-gem-a-quick-rundown/comment-page-1/#comment-5582 Ennuyer.net » Blog Archive » 2009-01-13 - Today’s Ruby/Rails Reading Tue, 13 Jan 2009 17:06:39 +0000 http://www.pathf.com/blogs/?p=1357#comment-5582 [...] Creating and Distributing your own gem: a quick rundown [...] [...] Creating and Distributing your own gem: a quick rundown [...]

]]> By: Patrick Reagan http://www.pathf.com/blogs/2009/01/creating-and-distributing-your-own-gem-a-quick-rundown/comment-page-1/#comment-5560 Patrick Reagan Mon, 12 Jan 2009 21:22:15 +0000 http://www.pathf.com/blogs/?p=1357#comment-5560 I've felt the same pain as you when creating Ruby gems that I want to distribute. I liked newgem for a while since it didn't include as much cruft as either hoe or bones (when using the --simple option), but it still felt a little too heavyweight for me. Since then, I set out to write a small command-line utility that would do the basics of building a gem directory structure that fit my needs and allow me to easily push to GitHub. I call it "simple-gem": $ sudo gem install reagent-simple-gem --source=http://gems.github.com $ simple-gem my_gem Assuming that you're using GitHub for code hosting, you just need to generate the gemspec and push: $ cd my_gem $ rake github $ git add . && git commit -m "Updated gemspec" && git push origin master More info is available on GitHub: http://github.com/reagent/simple-gem/tree/master/README.rdoc I’ve felt the same pain as you when creating Ruby gems that I want to distribute. I liked newgem for a while since it didn’t include as much cruft as either hoe or bones (when using the –simple option), but it still felt a little too heavyweight for me.

Since then, I set out to write a small command-line utility that would do the basics of building a gem directory structure that fit my needs and allow me to easily push to GitHub. I call it “simple-gem”:

$ sudo gem install reagent-simple-gem –source=http://gems.github.com
$ simple-gem my_gem

Assuming that you’re using GitHub for code hosting, you just need to generate the gemspec and push:

$ cd my_gem
$ rake github
$ git add . && git commit -m “Updated gemspec” && git push origin master

More info is available on GitHub:

http://github.com/reagent/simple-gem/tree/master/README.rdoc

]]>