On Mon, Dec 7, 2009 at 9:37 AM, Markus Roberts <[email protected]>wrote:
> >> Anyone have an issue with me upgrade the rspec version required by > >> Puppet's tests? > >> > >> 1.2.9 is out and seems to work fine, and someone *cough*Rein*cough* > >> wrote tests that required it somehow, so now I'm stuck with a conflict. > >> > >> I don't see any reason not to use more recent ones... > > > > Well, the latest one available in EPEL and in Fedora 12 is 1.2.7, so > > requiring anything newer than that makes it difficult to run the tests > > on those platforms. > > AFAIK, the current version is available for all platforms (rspec is > pure ruby--nothing in it is platform specific) so there should be > nothing difficult about running the most current version on any > platform. All you should need to do is pull down the gem and go. As > this is something that you should be doing on a directly controlled > machine (i.e., you won't be needing to install rspec on the clients or > anything) I'm not seeing where this presents a difficulty. > > -- Markus >From my perspective, for _development_ dependencies we shouldn't have to wait on system packages being updated -- even for dependencies with native code, as I think the use of RubyGems and build tools are a reasonable requirement for a development box. Obviously this is not the case for production dependencies. Cheers, Bruce -- Bruce Williams Developer @ Reductive Labs, 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.
