Bugs item #29169, was opened at 2011-05-05 18:56 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=29169&group_id=126
Category: other Group: None Status: Open >Resolution: Rejected Priority: 3 Submitted By: Kevin Olbrich (olbrich) >Assigned to: Ryan Davis (zenspider) Summary: rake creates ruby wrappers around non-ruby executables, causing them to fail Initial Comment: when providing executables with a gem, they get wrapped in a ruby wrapper that provides some support for using previous versions of a gem. If the executable is not a ruby file (e.g., a bash script, php, etc..) then the wrapper will fail. Suggestions: 1. allow the gemspec to force the gem to be installed with '--no-wrapper' and leave it to the developer to properly wrap executables. 2. check the shebang line of the executable and skip wrapping for anything that explicitly uses something other than ruby ---------------------------------------------------------------------- >Comment By: Ryan Davis (zenspider) Date: 2011-05-31 16:26 Message: I don't know of a good way to do this that works across platforms and makes sense. Rubygems is for ruby. If a file is in your gem's bindir and listed as a gem executable, it should be ruby. If your gem has "special needs" then it should do it out of band, like create a Rakefile that does your special steps for you and list the Rakefile as an extension in the spec. Or just use a post-install message telling people to install with --no-wrapper. Lemme know if I didn't understand something. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=29169&group_id=126 _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
