One gotcha In Windows 7 and Vista, when the working directory path ends with a 
symbolic link, the current parent path reference, .., will refer to the parent 
directory of the symbolic link rather than that of its target. This difference 
could break the importer code if it's playing with .. path components.
Another gotcha could be if you are creating a reparse point instead of a 
simlink. Reparse points aren't trasparent to applications, so the importer 
would need to be written to support reparse points a.k.a junctions.
In Windows I simply rename w2p's .git and .gitignore to .git-trunk and 
.gitignore-trunk then git init my app repo exactly where .git-trunk is. This 
way the two repos can physically co-exist but operationally they don't because 
only one of them can be named .git at any given time. So there's no chance of 
loosing app files when pulling w2p, nor need to worry about symlinks. The thing 
to keep in mind is switching to the right repo by temporarily renaming both of 
their folders, i.e., REN .git/ .git-apps/ && REN .git-trunk .git && git pull 
origin && REN .git .git-trunk && REN .git-apps .git (untested and don't forget 
.gitignore)

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to