symlinks - more issues with, part 3.

SoulseekQt-2015-5-26 on os x

soulseeqt **FOR OS X** resolves symlinks. it's not supposed to happen, symlinks are there for a reason, why on earth would you resolve them in an app, especially a p2p app.

example

you share the directory "/Users/<username>/Books", which contains symlinks to the actual storage location:

Books/eBooks -> /Volumes/zfs/nasdrives_1_2/Books/eBooks

soulseeqt resolves this link and shares

/Volumes/zfs/nasdrives_1_2/Books/eBooks/<dirs>

instead of /Users/<username>/Books/eBooks/<dirs>

what absolutely drives me around the bend is that there are 3 clients for soulseek from this developer, and each of the three handles symlinks differently, making it an absolute NIGHTMARE under mixed environments.

while i do understand the reason for not handling symlinks at all (even though i seriously disagree with it) as it happens with the Linux client i would at least expect all the clients from the same developer following the same philosophy, so you tackle the problem once and it's fixed from then on. having each client handle the issue differently is light-years beyond my understanding and forces users with more than the very simplest of needs to either emulate an official client under 2 platforms, or to use the non-official ones.