Here is what I've done. I split the tdesvn
package
into two packages
'tde-tdesvn' and 'tde-kiosvn' making tde-kiosvn a dependency
of tde-tdesvn and
of tde-tdesdk. Now the conflict is gone and both tdesvn and
tdesdk will pull in
kiosvn. The only remaining question is whether there is any
functional
difference in the kio_svn and kio_ksvn calls. Confirmation
of the packaging:
14:08 nirvana:~/tde/bld/tde-tdesvn> diff tdesvn-full.txt
tdesvn-nokio.txt
398,402d397
< tde-tdesvn
/opt/trinity/share/services/svn+file.protocol
< tde-tdesvn
/opt/trinity/share/services/svn+http.protocol
< tde-tdesvn
/opt/trinity/share/services/svn+https.protocol
< tde-tdesvn
/opt/trinity/share/services/svn+ssh.protocol
< tde-tdesvn /opt/trinity/share/services/svn.protocol
14:08 nirvana:~/tde/bld/tde-tdesvn> pacman -Qpl
tde-kiosvn-3513_tqt-1-x86_64.pkg.tar.xz
tde-kiosvn /opt/
tde-kiosvn /opt/trinity/
tde-kiosvn /opt/trinity/share/
tde-kiosvn /opt/trinity/share/services/
tde-kiosvn /opt/trinity/share/services/svn+file.protocol
tde-kiosvn /opt/trinity/share/services/svn+http.protocol
tde-kiosvn /opt/trinity/share/services/svn+https.protocol
tde-kiosvn /opt/trinity/share/services/svn+ssh.protocol
tde-kiosvn /opt/trinity/share/services/svn.protocol
Are you discussing how to handle building both packages on Arch or proposing Tim create a
new dependency package in the GIT source tree?
Darrell