Thanks Jens. That is a solid idea about the symlink. It also has the added benefit of being easy to rollback if Ferret 0.9 is not stable enough.
It may take me a few days to get around to testing this out, but I will post the details when I am finished in case others would like to give it a try. Tom On 4/3/06, Jens Kraemer <[EMAIL PROTECTED]> wrote: > On Mon, Apr 03, 2006 at 11:05:18AM -0400, Tom Davies wrote: > > Hi Jens, > > > > That looks promising and I will dig in to it when I have a chance over > > the next couple of days. However, looking through the comments people > > have had problems running it on Windows. Also, I am not sure if I can > > freeze a ferret gem that will work on both Windows and Linux. Do you > > think this would be possible? > > no, I think this won't be possible because of the compiled parts. The > Ruby-only version of ferret should work, though. > > Easy solution: switch to Linux for development ;-) > > > If not, i am leaning towards just tweaking my TextDrive setup to look > > for gems in an additional location that is outside of my deploy > > path... so I don't have to reinstall ferret every time I upload a new > > version of my application. > > don't know how to configure rubygems for that, Imho a rubygems > installation only looks for gems in the location specified at > installation time. > > I once had to re-install all gems after installing rubygems below > /usr/local, because it only looked for installed gems there. > I had another version of rubygems in /usr, with plenty of gems > installed, but the new rubygems did not find them. > > What about installing ferret into a lib/ directory inside your home > directory, and symlinking the contents of this directory into your > RAILS_ROOT/lib/ on deploy ? Should be easy to automate with capistrano, > formerly known as switchtower. > > Adding that lib dir to some Ruby library search path environment > variable could work, too. > > Installing your very own rubygems into your home dir would be another > option (see http://docs.rubygems.org/read/chapter/3 , section 3.2). > That would then look for gems in the location you specified as GEM_HOME, > but nowhere else, so you'd have to install all gems that you might need > into this private gems installation. > > Jens > > -- > webit! Gesellschaft für neue Medien mbH www.webit.de > Dipl.-Wirtschaftsingenieur Jens Krämer [EMAIL PROTECTED] > Schnorrstraße 76 Tel +49 351 46766 0 > D-01069 Dresden Fax +49 351 46766 66 > _______________________________________________ > Ferret-talk mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/ferret-talk > -- Tom Davies http://blog.atomgiant.com http://gifthat.com _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
