Tim, Darrell, All, During build of tdelibs, tdebase, there are a number of deprecation warnings. Do we want to capture these and track them to proactively address them in some fashion? Seems like a logical thing to do. That way when you are sitting around board and have nothing else to do, we have a list of things to work on :) Seriously, we currently have ffmpeg and cups issues to fix. We know there are samba changes coming soon, it might help to already take a look at what will need to be fixed and from what lib, etc.. Currently, tdebase has deprecated warning like: warning: 'bool KCModuleInfo::isHiddenByDefault() const' is deprecated (declared at /opt/trinity/include/kcmoduleinfo.h:179) warning: 'KeySym XKeycodeToKeysym(Display*, KeyCode, int)' is deprecated (declared at /usr/include/X11/Xlib.h:1695) warning: 'static KCModule* KCModuleLoader::loadModule(const QString&, QWidget*, const char*, const QStringList&)' is deprecated (declared at /opt/trinity/include/kcmoduleloader.h:78) warning: 'KMimeMagicResult' is deprecated (declared at /opt/trinity/include/kmimemagic.h:46) warning: 'KMimeMagic' is deprecated (declared at /opt/trinity/include/kmimemagic.h:101) warning: deprecated conversion from string constant to 'char*' /tdebase/kioslave/man/man2html.cp warning: 'static KSocketAddress* KExtendedSocket::localAddress(int)' is deprecated (declared at /opt/trinity/include/kextsock.h:997) warning: 'static int KExtendedSocket::resolve(KSocketAddress*, QString&, QString&, int)' is deprecated (declared at /opt/trinity/include/kextsock.h:967) warning: 'void libhal_storage_policy_free(LibHalStoragePolicy*)' is deprecated (declared at /usr/include/hal/libhal-storage.h:138) warning: 'char* libhal_volume_policy_compute_display_name(LibHalDrive*, LibHalVolume*, LibHalStoragePolicy*)' is deprecated (declared at /usr/include/hal/libhal-storage.h:344) warning: '_SMBCCTX::debug' is deprecated (declared at /usr/include/libsmbclient.h:2848) warning: '_SMBCCTX::_smbc_callbacks::auth_fn' is deprecated (declared at /usr/include/libsmbclient.h:2943) etc.... Just think about it. If it is something we would like to track, we could just dump a grep of the build logs into some format that makes sense to the project. May not be worth doing, but before I forgot about it, I thought I would propose it and let the smart people decide :) -- David C. Rankin, J.D.,P.E.