Hello, been using Toucan for a while now. Great tool!
I'm am simply trying to exclude a folder while performing a Sync operation. The preview shows the folder in the destination as red, which should mean that it will ignore the folder...
I get red lines in the log about not being able to create files (or folders, can't remember) that exist in the directory that is set to ignore.
My scenario:
-----------------------
P:\ *root*
\folder
\sync
\backup-pc-sync-folder *symbolic link to a network location*
\folder
Source: P:\
Destination: P:\sync\backup-pc-sync-folder
Exclude folder: sync (full path P:\sync has the same results)
-----------------------
I'm using these symbolic links (Win7) to network locations (I had trouble with Toucan and network paths...) so I don't have to map a drive on every PC I run Toucan on. I can simply point to one of the symbolic links.
This specific sync is my portable apps device. So you can see why I need to exclude the sync folder, since it's a subdirectory of the root...loops until disk space is consumed, haha.
So I'm not sure why the excluded path is being traversed.
this is tricky, it is traversed because you might have an include that means there are files that are included in that folder. I can definitely make this better than it is at the moment though, it should fix this case.
OK I see. I guess it's a rules precedence question then. Excludes trump includes?, visa versa.
Trying to think, maybe just having an absolute exclusion, non-traversal option (meaning don't look for includes in this exclusion) might work.
Not sure if the API you are using would expose symbolic links so you could have the option to ignore them. Plus that's a Win7 (Vista?) specific issue.
Sorry for this special case, but its a slick way to be "portable" without stupid mapped network drives.
I'm I correct on using network paths with Toucan? Don't seem to work... I could be doing something wrong. You would think with file abstraction, network files would just work, ha.
will definitely come up with something for this, you are right about it being a neat little solution! Indeed I probably ought to just get network paths sorted out once and for all