One issue about this approach: Can you do it with a gem that requires something to be installed in the operative system like openssl?
How do you manage that kind of dependecies? On Wed, Dec 10, 2008 at 11:54 AM, Simon Heywood < [EMAIL PROTECTED] <[EMAIL PROTECTED]>> wrote: > Seth, > hang on, bit slow here. Do you mean I can unpack the gems into the same > directory as my rb script, and then use the Shoes Packager to create an exe > for the whole directory and everything will be hunkydory? > > If so. Brilliant. > > Cheers, > > Si > > > > On Wed, Dec 10, 2008 at 3:53 PM, Seth Thomas Rasmussen < > [EMAIL PROTECTED]> wrote: > >> On Wed, Dec 10, 2008 at 4:34 AM, Simon Heywood >> <[EMAIL PROTECTED] <[EMAIL PROTECTED]>> wrote: >> > Where I work we use a pac file to determine the http proxy, which can >> vary >> > by location. HTTP_PROXY is not defined by default. Thus I have a slight >> > problem in distributing my app internally as it requires people to look >> at >> > the pac file and set HTTP_PROXY manually depending on their location. >> > **However**, the only reason I need HTTP_PROXY to be set is so that I >> can do >> > ===== >> > Shoes.setup do >> > gem 'hoe' >> > gem 'mechanize' >> > end >> > ===== >> > So, I wondered, as an alternative, if it would be possible for the >> Packager >> > to "Include required gems with app" along the lines of the "Include >> Shoes >> > with your app"? >> > However, I think platform specific gems might cause a problem here? >> >> It could be nice to automate this. In the meantime you can `gem >> unpack` into your project directory and just use require instead of >> Shoes.setup. >> >> -- >> Seth Thomas Rasmussen >> http://greatseth.com >> > >
