Bugs item #29169, was opened at 2011-05-05 20:56 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=29169&group_id=126
Category: other Group: None >Status: Closed 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: Kevin Olbrich (olbrich) Date: 2011-06-08 22:15 Message: https://github.com/rubygems/rubygems/issues/88 ---------------------------------------------------------------------- Comment By: Ryan Davis (zenspider) Date: 2011-06-07 18:50 Message: Hi! Believe it or not, we're moving to github's issue tracker! The pressure to move has been loud and clear, but for the longest time it didn't support the way we worked. Now that it has freeform labels it can support our workflow adequately. There is just one problem: Your bug is here and we don't want to lose you! What we'd like you to do is fairly painless and should only take a few minutes: Please file the _exact_ same ticket on github and provide a link back to this crufty old ticket so we can refer to any previous discussion that occurred. Once the new ticket is made, put a forwarding link to it here and close this ticket out. In a couple weeks, we'll track down the old tickets that are still open and decide what to do with them. We could have done this fairly automatically, but we really want you to do it so you're attached to the ticket and we can still communicate with you and keep a record of it. https://github.com/rubygems/rubygems/issues Thanks, The RubyGems Team ---------------------------------------------------------------------- Comment By: Ryan Davis (zenspider) Date: 2011-05-31 18: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
