[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 261926] amarok collection scan does not follow symlinks
From:       Craig Howard <kde () choward ! ca>
Date:       2011-01-05 3:31:00
Message-ID: 20110105033100.3C4E97A25B () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=261926





--- Comment #2 from Craig Howard <kde choward ca>  2011-01-05 04:30:57 ---
I'm surprised to hear that.  On a unix platform, the client software has to
take special action to see the symlink instead of the contents of the file.  I
dug in a bit.

In CollectionScanner::readDir(), this seems to be the line killing me:

 384         const QFileInfo &f = fi.isSymLink() ? QFileInfo(
fi.symLinkTarget() ) : fi;

I found some old discussions about being careful about multiple symlinks
pointing to the same file, but could there not be a config option in amarok
(and corresponding flag in amarokcollectionscanner) to determine if this line
should be run for those that know their symlinks only point to a single file,
or prefer proper symlink semantics?  I'm pretty sure this would solve my
problem, but I don't have a dev environment setup to test it at the moment.  Am
I missing something?

I'm surprised to see this marked as wishlist, as this particular bug makes
amarok unusable for me (my collection has zero items).  The old discussions
seem to indicate amarok 1.x had this ability.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]