[SERVER-522] Temporarily undo `puppetserver gem env` fix from SERVER-262 Created: 2015/03/26 Updated: 2015/04/21 Resolved: 2015/03/26
|Affects Version/s:||SERVER 1.0.2|
|Fix Version/s:||SERVER 1.0.3|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
The fix that was done for
The new behavior for GEM_PATH created concern for some that users might encounter confusion around the following possible scenario:
1) User had a value set in the external environment for GEM_PATH which included a directory where the MRI/system Ruby would install / look for gems.
2) User had used the MRI/system Ruby gem command to install a gem into that directory, e.g., "nokogiri."
3) User ran "puppetserver gem list" and saw that "nokogiri" appeared to be installed. In this case, it would be the "nokogiri" to be used with MRI/system Ruby, not a JRuby-compatible "nokogiri" - however, this distinction may not be obvious to the user.
4) Assuming that the "nokogiri" gem had properly been installed for Puppet Server to use, user starts Puppet Server service. Some of the user's Ruby code that references "nokogiri" would blow up because "nokogiri" couldn't be found via either GEM_HOME or GEM_PATH.
Rather than rework the initial work done for