TRANS wrote: > While I think the proposal is probably the right one, just to draw > soem contrast the other option is to keep the datadir in the gem and > provide access to it, eg. > > Gem.datadir( 'mygemsname' )
The disadvantage of this approach is that it then requires the software to be installed as a gem to run. If the Config::CONFIG['datadir'] value is used, you don't have any dependencies on gems. Also, anything in the gem directory must also be considered read-only by the application (just like datadir). -- -- Jim Weirich [EMAIL PROTECTED] http://onestepback.org ----------------------------------------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas) _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
