Bug 143527 - konqueror filemanager cannot produce relative symlinks
Summary: konqueror filemanager cannot produce relative symlinks
Status: RESOLVED FIXED
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.9.2
Platform: Chakra Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
: 224396 325926 351911 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-03-27 23:47 UTC by Janet
Modified: 2018-04-17 21:50 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Janet 2007-03-27 23:47:17 UTC
Version:           3.5.6 (using KDE 3.5.6, Debian Package 4:3.5.6.r1.dfsg.1-2 (4.0))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.20.4-slh-up-1

Case 1: Konqueror's servicemenus aren't executed relative from the directory they are called from but use absolute paths.

e.g. when I want to symlink file /home/me/dummy.txt to /home/me/dummy2.txt there are 2 ways from konsole:
1. ln -s /home/me/dummy.txt /home/me/dummy2.txt produces an absolute symlink dummy2.txt which points to /home/me/dummy.txt
2. assumed I am in /home/me: ln -s dummy.txt dummy2.txt: produces a relative symlink dummy2.txt which points to dummy.txt

Now lets try it with a servicemenu:
e.g. with the line: Exec=ln -s %u %u2

I would expect that produces a relative symlink because I call ln -s from within the directory where file and symlink are and the command has the same structure as the command executed from konsole.
But instead an absolute symlink is created - which is useless and contraproductive e.g. when you want to copy the file and symlink together to another directory or tar it to give it away (the absolute symlink gets broken and is useless on another persons computer). 

Case 2: Konqueror has the same problem when I create a symlink in the same directory by dividing the window and drag-n-drop the file to the other side - though it's the very same directory an absolute symlink is created.

Expected behaviour: When I create a symlink in the same directory konqueror should create a realive symlink without path. And servicemenus should also use relative paths.
Comment 1 Shriramana Sharma 2007-11-04 16:02:42 UTC
Wish I could confirm this. It's really irritating. Give us a config option allowing us to choose one of the following:

1) Always create absolute symlinks
2) Always create relative symlinks
3) Ask at creation time
Comment 2 Janet 2007-11-04 20:31:18 UTC
To ask would be the best solution I guess. When you drag a file you choose between move/copy/symlink - maybe that can be extended: move/copy/relative symlink/absolut symlink (or instead of relative/absolute "with path" and "without path").
Comment 3 Janet 2010-12-05 07:53:16 UTC
Can someone please assign this to dolphin?
Comment 4 Martin Koller 2011-06-04 21:17:04 UTC
confirmed in 4.6.3
Comment 5 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:19:50 UTC
Resetting assignee to default as per bug #305719
Comment 6 Frank Reininghaus 2012-11-06 18:05:57 UTC
I don't think that is actually a Dolphin issue. AFAIK, creation of symlinks is handled in KIO::CopyJob.
Comment 7 Christoph Feck 2013-10-12 15:20:57 UTC
*** Bug 325926 has been marked as a duplicate of this bug. ***
Comment 8 Christoph Feck 2014-05-04 17:36:27 UTC
*** Bug 224396 has been marked as a duplicate of this bug. ***
Comment 9 Frank Reininghaus 2015-08-29 18:45:44 UTC
*** Bug 351911 has been marked as a duplicate of this bug. ***
Comment 10 Frank Souza 2016-10-17 02:41:10 UTC
The bug persists:

Arch Linux 64

dolphin 16.08.1

KDE Frameworks 5.26.0
Qt 5.7.0 (compiled with 5.7.0)
xcb windows system
Comment 11 Nate Graham 2018-04-17 21:50:57 UTC
Dolphin is able to create relative symlinks using KIO; calling this fixed as of KDE Frameworks 5.46 and Dolphin 17.12.3.