Source Compatability and DCOP

Ian Reinhart Geiser geiseri at yahoo.com
Wed Aug 7 15:40:28 BST 2002


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi
	I noticed KAddressbook changed its dcop interface in a Source Incompatible 
manner.  This i guess broke KPilot, but worse it seems to have broken a few 
scripts I had done for a client for adding information to their addressbook 
from my TWIG web mail interface. 

	Is there a policy on breaking DCOP interfaces on sub releases?  Is the fact 
that KAddressbook is not in kdelibs make it okay to change on subreleases? Is 
it too late to fix this problem?  

	Just wondering as I need to know if I should warn my client not to upgrade 
from KDE 3.0.x

	Thanks
	-ian reinhart geiser
- -- 
========================================
All progress is based upon a universal innate desire on the part of
every organism to live beyond its income.
		-- Samuel Butler
========================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9UTFcPy62TRm8dvgRAu7MAKDgHWqcWWi5uFnG0nlkx9nm20z3MACfTQci
SNIxy/DB95HfejwENzoM2lw=
=qwMh
-----END PGP SIGNATURE-----





More information about the kde-core-devel mailing list