Issue #16757 has been updated by Josh Cooper.

Status changed from Needs Decision to Merged - Pending Release
Affected Puppet version set to 0.25.0
Keywords set to rubygems bundler gemfile gem

Merged into 3.0.x in 577d633f6f60ea72a0a933c9323fba74cc101382

If bundler is loaded, e.g. `bundler exec puppet`, then don't load rubygems, 
since bundler has its own logic for managing gems in the current application 
environment. And the set of gems, versions, etc is often different than what 
gems you may have installed, via rvm for example.

If bundler is not loaded, fall back on the old behavior, which is to ensure 
rubygems is loaded before calling any puppet code. Ideally, this should be done 
in the `bin/puppet` script, however, that doesn't work for rack setups, so we 
moved rubygems loading to the command line code, which is effectively the 
puppet application entry point.

Several features, e.g. stomp, were calling `Puppet.features.rubygems?` only for 
its side-effect of loading rubygems before evaluating the calling feature's 
gems. This is no longer necessary now that we ensure the gem loading system is 
sane early on.

Custom features may be calling `Puppet.features.rubygems?`, so we've added a 
deprecation warning and preserved the old behavior (of explicitly requiring 
rubygems). It may be necessary to modify custom features in order to ensure 
puppet works correctly in a bundler environment.
----------------------------------------
Bug #16757: user cannot control loading of rubygems
https://projects.puppetlabs.com/issues/16757#change-72908

Author: Patrick Carlisle
Status: Merged - Pending Release
Priority: Normal
Assignee: eric sorenson
Category: 
Target version: 3.0.1
Affected Puppet version: 0.25.0
Keywords: rubygems bundler gemfile gem
Branch: 


Puppet requires rubygems throughout the code, as well as in libraries it 
depends on (hiera and facter), making it impossible for a user to turn off 
rubygems. This can make puppet especially slow with the new rubygems loading in 
3.0.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" 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-bugs?hl=en.

Reply via email to