We have the following structure for development files under subversion: trunk |_ someproject |_ media branches |_ somebranch |_ someproject |_ media
I have a symlink from trunk/someproject to site-packages/someproject on my machine. I need to launch the branched version of the project at the same time. So intuitively I create a symlink from branches/somebranch/someproject to site-packages/someproject2 to get it to the python path. When I try to run the shell for the project, the settings file from someproject is taken instead of someproject2: the symlink is followed and the real name of the linked directory is used instead of the name of the symlink. The only solution that I came up with was to rename someproject to someproject2 in the somebranch and then to create a symlink from branches/somebranch/someproject2 to site-packages/someproject2 (notice the matching names). But in that case I won't be able to merge the branch back to the project, will I? How do you solve problems like that, or how could I deal with it instead of renaming the project? Regards, Aidas Bendoraitis [aka Archatas] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
