Gems Being Installed but the Symlink for the Executable is Not Created
53 views
Skip to first unread message
Navid Paya
unread,
May 8, 2014, 10:06:54 PM5/8/14
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to ansible...@googlegroups.com
Hi guys
I'm using ansible to deploy the scoutapp.com agent which is basically a ruby gem. I have used both the gem and shell modules to install the module, the problem is after the module is installed, the executable isn't symlinked to a location like /usr/bin or /usr/local/bin which is what would happen if I run the exact same command in a shell. I know ansible runs this stuff using a Python script so I was wondering if you know anyway I can fix this?
This is my instructions:
- name: Install the scout gem
shell: gem install scout -no-rdoc -no-ri
And this is the one I tried with the gem module:
- name: Install the scout gem
gem: name=scout state=present
Dick Davies
unread,
May 9, 2014, 11:43:36 AM5/9/14
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to ansible list
Look at the 'user_install' option on the gem task.
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to ansible...@googlegroups.com, di...@hellooperator.net
Thanks, Dick. That did the job. Actually I saw this option but thought it would work the other way around (as in if set to yes, it would create the executable). It's working like a charm now.