> not sure if there's a way to tell rpmbuild to do that, but you can
> just comment them out in the spec file. or when you install you can
> do rpm -ivh --nodeps to skip them.
>
> There's a ticket open to make this kind of thing easier - being able
> to rebuild the rpms for different rubies installed in weird places
> but I havnt really had any good thoughts about how to achieve that.
> --
> R.I.Pienaar
This allowed me to get the product installed; however, it failed
with the /usr/bin/env -- so when I ran the commands, the 'require' for
mcollective didn't work (presumably because the installation wasn't
done properly, as it would have installed into the Enterprise Ruby
directory.
The Enterprise Ruby executable is in my $PATH -- though the PATH
variable points to a symlink that goes to the full version named
directory -- shouldn't make a difference here.
Shouldn't the mcollective tarball have a script to facilitate a
manual install? That would be a good place to override/set some
variables.
Thanks...
--
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.
