RubyScript2Exe works great when working with gems. I never has any problems using any gem, but I thÃnk RubyScript2Exe
includes a bit "too much" when using gems. Many gems uses lots of examples and provides much documentation,
something that really isn't that useful when running the gem "inside" an exe.
It would be great if it would be possible to narrow the default parts of a gem that should be included with an .exe.
The lib, ext (and perhaps bin) subdirectories are always needed, but very few gems require any more sudirectories to
work.
To allow greater choice I propose that some variables are used to control what gets included, ie:
RUBYSCRIPT2EXE.gem_include_dirs=:core|:full|:custom
:core - includes lib, ext (bin) - This should be default
:full - includes full gem (as today)
:custom - See below
If using custom, the user should be able to specify what directories that should be included. The core dirs shouldn't
have to be included in the array
RUBYSCRIPT2EXE.gem_include_custom_dirs = [array of custom dirs]
Anyway, this is only a suggestion. I make use of RubyScript2Exe almost every week and I think it's a great program.
Thank you for making it available to the world! |