On 09/22/2012 03:21 AM, jdehnert wrote:
I'm aware of the issues of installing software through source vs. pkg
management systems. I should have mentioned that I've been in IT for
over 20 years. Its just puppet and ruby that are new to me, but I'm
learning fast. We are in agreement about sticking to one type of
package management. It much easier now that it was back when I was
installing SunOS 4.1.4 on Sun 3's and Sparc 2's and compiling X11 from
source.
If you were really aware, then you wouldn't do it...
I've considered all of these. Does anyone know of a CentOS/RH repo that
has the latest versions of Ruby available? I have done some searching,
but not exhaustively so, for a repo with the most recent versions of
Ruby, but no luck so far. The reason I want to use ruby-1.9.2-p320 on
these test VM's is because in the production environment that these are
mimicking the engineering folks are running that release, under RVM, and
they want to avoid any installs of other versions to eliminate any
chance of something getting pointed to an older version of Ruby
accidentally. The dev and production environments will both point to
Ruby under RVM.
This is wrong approach. Try to figure out why is RHEL/CentOS and Suse
Enterprise sticking to older version of ruby (or every other piece of
software they distribute), and what are the benefits...
I was hoping someone might know some details about the rpm system that
might allow me to tell it that ruby was installed without installing
ruby, as with fake sendmail. Perhaps a lesser known tool that allows one
to insert entries into the rpm database files.
You are mangling with the system in a way it shouldn't be mangled with.
Try to persuade your developers to use platform that is already used on
production, and not vice versa.
If that doesn't go quite right, then take src.rpm from RedHat/CentOS,
bump version to 1.9.x - or whatever do you want to use, drop in newer
sources, fix patches - and rebuild the RPM - or try to backport latest
feodra build:
http://fedora.aau.at/linux/releases/17/Fedora/source/SRPMS/r/ruby-1.9.3.194-10.1.fc17.src.rpm
but that could bring you back to trouble because that version probably
won't be 100% identical to the one that your dev team uses (if they
stick to sources). So we're back to square one - you *have to* convice
your team to use Ruby from RPM package - either fedora backport or
standard RHEL 1.8.x.
Everything else _*will*_ bit you in the ass in the long run.
--
Jakov Sosic
www.srce.unizg.hr
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
