Issue #7441 has been updated by Adam Edwards.
It seems like a lot of extra work to try and create separate packages for SLES. I run a 50% mix of SLES/RHEL in my enterprise (600+ servers) and there are lots of noarch packages that work out of the box on both. Since there is no compiled code in mcollective, I think it would be less maintenance to support only one spec/srpm. Any discrepencies between the environments can be handled by configuration files. For example, what about having /etc/init.d/mcollective read a configuration file in /etc/mcollective/mcol.conf, then if RUBYLIB is different on my environment I can just update the configuration file. How can I help get it to be a supported platform? SLES is probably the second most used enterprise system behind RHEL/CentOS ---------------------------------------- Bug #7441: /etc/init.d/mcollective fix https://projects.puppetlabs.com/issues/7441 Author: Adam Edwards Status: Needs More Information Priority: Normal Assignee: R.I. Pienaar Category: Packaging Target version: Keywords: Branch: Affected mCollective version: In SLES 11, the RUBYLIB dir is a little different than RedHat. Would you be able to make the following code change so that it works on SLES out of the box? /etc/init.d/mcollective script as follows: Old: RUBYLIB=/usr/local/lib/site_ruby/1.8:$RUBYLIB New: RUBYLIB=/usr/local/lib/site_ruby/1.8:/usr/lib/ruby/site_ruby/1.8:$RUBYLIB -- 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.
