[Rubygems-developers] RubyGems don't like binaries for executables
Daniel.Berger at qwest.com
Tue Oct 23 17:10:08 EDT 2007
> -----Original Message-----
> From: rubygems-developers-bounces at rubyforge.org
> [mailto:rubygems-developers-bounces at rubyforge.org] On Behalf
> Of Luis Lavena
> Sent: Tuesday, October 23, 2007 2:21 PM
> To: rubygems-developers at rubyforge.org
> Subject: [Rubygems-developers] RubyGems don't like binaries
> for executables
> This behaviour is old:
> Add an executable (binary compiled for the platform) to
> <gem>/bin and later include this in the default_executable /
> executabels option of the specficication.
> What happens: when you install the gem, RubyGems
> systematically add the shebang to all the files marked as
> executables (and create the windows stubs also).
> To workaround this, I needed to exclude mongrel_service.exe
> from executables and manually copy the file, which is sub
> optimum (actually my gem does it).
> The problem with this is that you can't have 2 versions of
> the same executable laying in your ruby/bin folder, and also
> is sub optimum create batch scripts that load ruby, rubygems,
> get the correct version and #system to the executable with
> the ARGV list...
> Also, for this case, mongrel_service register a service in
> the windows registry, so:
> is part of the action command line, which will brake with
> later updates of the gem.
> What other developers suggest about this? Or I should stay
> away the patching nightmare and keep doing what I currently do?
If I understand correctly, executables are not put in c:\ruby\bin,
correct? Is there an option to copy or move executables to the ruby/bin
directory automatically (or wherever the user wants to put executables)?
If not, perhaps an option to add that would be nice. If it already does
that, then I'm afraid I don't understand the issue.
This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.
More information about the Rubygems-developers