https://bugs.kde.org/show_bug.cgi?id=424340
Russell Haley <yumpusamongus+...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yumpusamongus+...@gmail.com
Resolution|FIXED |---
Status|RESOLVED |REOPENED
--- Comment #3 from Russell Haley <yumpusamongus+...@gmail.com> ---
The "fix" has created the opposite problem -- the bookmarks.xml file has
absolute paths in it, which I discovered with a precautionary recursive grep
before re-aiming a symlink to a new mount point. These would've broken had I
not found them.
IMO, looking "behind" symlinks is not something applications should do except
to avoid loops or protect users from themselves, such as a text editor unsaved
modifications to open files. Resolving and storing absolute paths like this
seems to defeat the intent of the user/admin who created the symlink. Do I
need to start bind mounting instead?
--
You are receiving this mail because:
You are the assignee for the bug.
