[Rubygems-developers] Executing code after installing gem

James Tucker jftucker at gmail.com
Tue Nov 25 08:37:22 EST 2008

On 25 Nov 2008, at 12:39, Matt King wrote:

> 2008/11/25 Luis Lavena <luislavena at gmail.com>:
>>> Well because it's not something a user will execute at the CLI,  
>>> it's a
>>> required executable by the gem itself in order for some  
>>> functionality
>>> to work.
>> By required executable you mean a binary? Or you're calling/shelling
>> out to another ruby script that you bundle?
>> If you provide more information (ala: details) will be much more easy
>> for us to contribute ideas to proper implement this without guessing
>> :-)
> Alright, so the gem is a Rails app that gets symlinked from several
> directories. The app uses background_job (bj), and in the gem there is
> a jobs/ folder. background_job requires all of these files within this
> directory to be world executable. And it must live in the jobs/
> folder. It never gets executed by a user at the CLI, but when a job is
> submitted via the Rails app, it spins it off using the corresponding
> files in this folder.
> Additionally, although I have it world executable before building the
> gem, it doesn't seem to stick when I actually build it.

Right, rubygems doesn't seem to maintain executable bits for files not  
in the executable list.

Don't you need a general install via rake anyway (like rake db:migrate)?

In which case surely something like:

task :install => %w[db:migrate jobs:chmod]


> Thanks for the help,
> -Matt
> _______________________________________________
> Rubygems-developers mailing list
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers

More information about the Rubygems-developers mailing list