On Sat, Mar 8, 2008 at 10:54 AM, Daniel Brumbaugh Keeney <[EMAIL PROTECTED]> wrote: > I agree with your solution, that it should be possible to have a Ruby > script, included in the gem, should be executed after installation of > the gem. That permits the use of arbitrary programs for documentation, > such as rdoc, or other install procedures, such as adding menu items, > currently not possible during RubyGems' install process. This, as > well, I consider to be a major flaw in RubyGems, which a post-install > script would cleanly solve. Of course, this would also require a > pre-removal script, and it is important to consider the authority > these scripts will be given. Basically, I think it's a fantastic idea.
My understanding is that it's a security feature as to why arbitrary scripts aren't executed in a RubyGems install. It can be worked around by making an "extension" that does this, but that is considered bad form (and if a "reviewed repository" concept similar to RPA is ever implemented, would be grounds for *not* including such a gem). I would be opposed to post-install/pre-remove scripts just for that reason. (It may also more tightly bind RubyGems to its current directory structure.) -austin -- Austin Ziegler * [EMAIL PROTECTED] * http://www.halostatue.ca/ * [EMAIL PROTECTED] * http://www.halostatue.ca/feed/ * [EMAIL PROTECTED] _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
