On Friday, September 21, 2012 7:59:46 AM UTC-7, jcbollinger wrote:

>
> You have a wrong concept: yum and rpm don't care whether any particular *
> software* is installed, they care only about what *packages* (RPMs) are 
> installed.  That's why they don't care about the Ruby you've installed via 
> rvm.
>
> As a system administration principle, I think it's a rather poor idea to 
> install software other than via the system's native package management 
> system.  Among other things, that means I have no use for rvm (or gem), and 
> also that I build a fair number of packages myself.  If you ignore that 
> principle, then you need to be aware that you thereby start down a slippery 
> slope; in fact, you are beginning to discover that on your own.
>

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.
 

> So what can you do?  Here are some of your options:
>
> 1) Use the system's Ruby packages.
>
> 2) Build and install your own Ruby packages (you can probably find some 
> source RPMs to adapt)
>
> 3) Download the Puppet source and install it manually
>
>
> John
>

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.

I ran into an issue like this once before where I needed to compile the 
latest version of Postfix to get access to a feature that was in the latest 
release.   Bit too soon after I ran into rpm prereq issues because the rpm 
system was saying that no mta was installed.  I eventually found a fake 
sendmail package, that installed nothing, but told rpm that sendmail was 
installed and that resolved the prereq issue without actually installing 
anything.

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 received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/Hzg7HtK6FtkJ.
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.

Reply via email to