I think an immediate and mutually satisfactory solution is to use a ">=" version specification that allows infrequent patchers using an older version of Rspec to contribute easily (which we obviously want) and allows frequent contributors to use their (most likely) up-to-date Rspec version without undue frustration (which we obviously want).
Also, Rubygems and your normal packaging system certainly don't work well together and, as I have suggested in the past[1], it is best to not ask them to. Luckily, Rubygems can be installed in and used from a user's home directory quite easily and with a minimum of configuration[2], which should make it quite feasible for most people to have their cake and eat it too. And by cake, I mean Rubygems. [1] https://help.ubuntu.com/community/RubyOnRails [2] http://docs.rubygems.org/read/chapter/3#page83 -- Rein Henrichs http://reductivelabs.com -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
