Revision history [back]
You do not want to use /usr/lib/wingide6 as WINGHOME. Instead, use some other directory that the user on the remote host can write to. In this case, the problem is that Wing is trying to write additional files to WINGHOME and fails to do that. The directory you choose for the remote WINGHOME should not exist, or should be empty, but the parent directory does need to exist. For example, if /home/myuser is the home directory of the user you are sshing in as, /home/myuser/winghome would work fine.We'll try to clarify that WINGHOME should no longer be a Wing install, or more likely will just automate this. Earlier in the design of this system is was OK to use the Wing install directory on the remote host but it no longer works. Thanks for pointing out that potential source of confusion!
You do not want to use /usr/lib/wingide6 as WINGHOME. Instead, use some other directory that the user on the remote host can write to. In this case, the problem is that Wing is trying to write additional files to WINGHOME and fails to do that. The directory you choose for the remote WINGHOME should not exist, or should be empty, but the parent directory does need to exist. For example, if /home/myuser is the home directory of the user you are sshing in as, /home/myuser/winghome would work fine.We'll try to clarify that WINGHOME should no longer be a Wing install, or more likely will just automate this. Earlier in the design of this system is was OK to use the Wing install directory on the remote host but it no longer works. Thanks for pointing out that potential source of confusion!