[PATCH] Multi-Protocol IO-Slave

Kevin Krammer kevin.krammer at gmx.at
Sun Jan 13 18:57:46 GMT 2008

On Thursday 10 January 2008, nf2 wrote:

> This patch has no effect on the behavior of KIO unless a Multi-Protocol
> IO-Slave .protocol file is installed. The aim of this patch is to allow
> to develop and test bridging into a cross-desktop network-transparency
> library without having to recompile or repackage kdelibs/kdebase
> (without having to remove .protocol files of the original IO slaves).

Sorry for replying to the top posting again, but isn't is sufficient to use 
KDE's layered resource framework for this?

Usually during development the prefixes where KDE is installed and where 
software under development is installed to are different anywhere, so the 
only requirement AFAIK is to have the development install prefix listed 
before the KDE main prefix in KDEDIRS.

So if for example KDE was being used unchanged from official packages sources 
and installed in /usr, any .protocol file referring to the multiprotocol 
slave installed into /usr/local would be the one used when KDEDIRS would be 
setup like this


It might even be possible to just symlink the multislave binary to the names 
of the standard slaves and not install any .protocol files at all.

Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20080113/17e455f0/attachment.sig>

More information about the kde-core-devel mailing list