[typo] being stupid with Enterprise Ruby and Typo from github
tobias.weisserth at gmail.com
Tue Feb 24 11:19:09 EST 2009
You are 100% right.
vendor/rails exists and is emtpy. Deleting it magically "unlocks"
After deleting the empty vendor/rails directory I did a "git status" which
returned no modified files. Is this git standard behaviour to not track
directories? In this case, that was the cause of a lot of trouble. I checked
out typo from github with the vendor/rails directory existing. It would be
best I guess to delete it upstream.
As soon as I'm back home I am also going to update the Typo Wiki on github
as to what gems you need to have so typo will work after checkout.
On Tue, Feb 24, 2009 at 3:39 PM, Matijs van Zuijlen <matijs at matijs.net>wrote:
> Tobias Weisserth wrote:
>> (in /home/tweisser/workspace/typo/typo)
>> rake aborted!
>> no such file to load --
> This sounds like the ./vendor/rails directory exists: If it exists, rails
> will try to load itself from there even if you tell it to use the gem in the
> configuration file.
> Can you check if this directory exists? It should be empty. If it is, can
> you remove it and try again?
> Typo-list mailing list
> Typo-list at rubyforge.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Typo-list