----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/105831/#review16814 -----------------------------------------------------------
"Actually we need to test both source and destination to check if their protocols support symlink creation." Haha, if we're copying a symlink, then obviously the source protocol supports symlinks, otherwise it wouldn't be there in the first place :-) - David Faure On Aug. 2, 2012, 9:31 p.m., Lamarque Vieira Souza wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://git.reviewboard.kde.org/r/105831/ > ----------------------------------------------------------- > > (Updated Aug. 2, 2012, 9:31 p.m.) > > > Review request for kdelibs. > > > Description > ------- > > Some kio protocols support creating symlinks but a change in > kio/kio/copyjob.cpp hardcoded symlink creation to only when source and > destination protocols are the same. That change was added to fix a problem > with ftp protocol creating symlinks instead of copying files (there is a > comment in the source code about that). I think instead of forcing source and > destination use the same protocol we should test if the destination protocol > supports creating symlinks (ftp protocol does not). That would allow kio's > like fish and nfs create symlinks. I am also working on some other changes > that could use this feature. > > > Diffs > ----- > > kio/kio/copyjob.cpp 8dde763 > > Diff: http://git.reviewboard.kde.org/r/105831/diff/ > > > Testing > ------- > > > Thanks, > > Lamarque Vieira Souza > >
