What's the new hotness for packaging gems?
in [Ruby]
|
Prev: app/helpers in Rails
Next: Oracle-oci8.2.0
From: Matt H on 29 Nov 2009 12:11 On Sat, Nov 28, 2009 at 10:14 PM, James Edward Gray II <james(a)graysoftinc.com> wrote: > On Nov 28, 2009, at 10:42 PM, Roger Pack wrote: > >>> In this age of Gemcutter, what should I be using to generate my >>> gemspecs/build my gems/etc? >> >> jeweler is what I'm using these days. > > I've seen several uses of it now and it always strikes me that it's just about the same size as a traditional gem specification. Which problem were we trying to solve with all of these fancy packagers again? :) > Jeweler is pretty awesome because in addition to providing rake tasks like: rake version:bump rake gemcutter:release It will also automatically create your repository on github if you're into that. I haven't tried the others though. -- Find me - http://www.smajn.net/social
From: David Masover on 29 Nov 2009 14:26 On Saturday 28 November 2009 11:14:10 pm James Edward Gray II wrote: > On Nov 28, 2009, at 10:42 PM, Roger Pack wrote: > >> In this age of Gemcutter, what should I be using to generate my > >> gemspecs/build my gems/etc? > > > > jeweler is what I'm using these days. > > I've seen several uses of it now and it always strikes me that it's just > about the same size as a traditional gem specification. Which problem > were we trying to solve with all of these fancy packagers again? :) Mostly kidding, too, but I have to agree -- the only gems I've actually built lately have been small enough that I don't see a real advantage to doing it programmatically. The last time I did, the only real point I saw was getting a list of files -- only needed when I was letting Github build gems, and directory globbing was not allowed in those gempsecs.
From: Ryan Davis on 29 Nov 2009 16:30 On Nov 28, 2009, at 14:25 , Tony Arcieri wrote: > I've used ad hoc stuff for packaging most of my gems. Long ago there was > hoe... is that still relevant? > > In this age of Gemcutter, what should I be using to generate my > gemspecs/build my gems/etc? Hoe is still very relevant and is what pretty much all of seattle.rb uses. It has a great plugin system that makes it very easy to enable extra features. Raggi wrote a gemcutter plugin that'll be folded in and default on the next release.
From: Roger Pack on 30 Nov 2009 14:34
>> jeweler is what I'm using these days. > > I've seen several uses of it now and it always strikes me that it's just > about the same size as a traditional gem specification. Which problem > were we trying to solve with all of these fancy packagers again? :) > > I'm mostly kidding here. Everyone should use whatever they like, of > course. Yeah now that we no longer publish through github it's not as much of a necessity. It does still give you the s.add_development_dependency 'x' it will break that up into the appropriate dependency based on rubygems version (i.e. it gives you the backwards compatible checks for free), but beyond that you could probably just stick it in a gemspec anyway. -r -- Posted via http://www.ruby-forum.com/. |