KTp/Packaging Guide: Difference between revisions

Revision as of 14:36, 7 November 2011

Packaging KDE-Telepathy is complicated for two reasons: firstly, due to the modular nature of Telepathy, there are several distinct components in separate git repositories. Secondly, there are large numbers of runtime interdependencies to worry about. This page attempts to ease packaging KDE-Telepathy in a useful way by explaining these issues.

Upstream Packages

Two upstream packages are essential for KDE-Telepathy to work.

telepathy-qt4 >= LATEST (currently 0.7.4, Build and Runtime Dependency)
telepathy-mission-control >= 5.7.9 (Runtime Dependency)

We're also using some bits from kdelibs 4.7.0 (Build and Runtime Dependency).

The IM networks that KDE-Telepathy can connect to are decided by which Telepathy Connection Managers are installed. These are runtime only dependencies, but which ones are installed will decide what IM networks KDE-Telepathy supports. The following are the ones we recommend - whether they are installed optionally or required is, of course, up to you.

telepathy-gabble 0.13.7 (for Jabber support, including Google Talk and Facebook, might very probably crash with earlier versions)
telepathy-butterfly (for MSN/Windows Live support)
telepathy-haze (for all the other protocols, as supported by libpurple).

KDE-Telepathy Packages

The different components of KDE-Telepathy are housed in separate git repositories on projects.kde.org. Some of these components are currently recommended to use. Others are not yet ready to be installed by users.

Ready Components

These components have reached a level of maturity where they are interesting to users. We recommend providing these components at the current time.

Name	Description	Dependencies
telepathy-kde-accounts-kcm	Account management KCM	telepathy-qt4, data from telepathy-kde-contact-list (at runtime)
telepathy-kde-approver	KDED module that shows a notification when somebody starts a chat with you	telepathy-qt4, data from telepathy-kde-contact-list (at runtime)
telepathy-kde-text-ui	Text chat application	telepathy-qt4, data from telepathy-kde-contact-list (at runtime)
telepathy-kde-contact-list	Contact list application - Also provides icons and other data files that are shared among the other applications	telepathy-qt4
telepathy-kded-module	Workspace integration module - provides several plugins like auto-away, the infamous 'Now listening to...' and also an error handler (important!!)	telepathy-qt4
telepathy-kde-presence-dataengine	Plasma dataengine that provides telepathy data to plasmoids	telepathy-qt4
telepathy-kde-presence-applet	Plasma widget for setting your online presence - acts as the central system tray icon of traditional IM clients	telepathy-kde-presence-dataengine (at runtime), data from telepathy-kde-contact-list (at runtime)
telepathy-kde-filetransfer-handler	Background application for handling file tranfers	telepathy-qt4
telepathy-kde-auth-handler	Background application for handling passwords and ssl certificates	telepathy-qt4
telepathy-kde-send-file	Dolphin/konqueror context menu plugin for sending files easily to contacts	telepathy-qt4, telepathy-kde-filetransfer-handler (at runtime), data from telepathy-kde-contact-list (at runtime)

Required components for basic functionality: telepathy-kde-accounts-kcm, telepathy-kde-contact-list, telepathy-kde-text-ui, telepathy-auth-handler, telepathy-kded-module

Highly recommended components (should be installed by default): telepathy-kde-approver, telepathy-kde-presence-applet, telepathy-kde-presence-dataengine, telepathy-kde-filetransfer-handler

Optional components: telepathy-kde-send-file

Experimental Components

We have several other components under development, however, unless they are listed above we do not recommend packaging them. This is because they are subject to major changes/removal at any time, and are not ready for end users yet.

Release Tarballs

The latest release is the 0.1.0 Technical Preview release. As its name suggests, this is a technical preview and is by no means considered a proper stable release.

Tarballs can be found at the KDE ftp mirrors: http://download.kde.org/download.php?url=unstable/telepathy-kde/0.1.0/src/

Distributions

Here is a list of known packaging efforst for various distributions. If you are also doing packages for a distribution, add your information here.

Distro	Packager	Links
Debian	George Kiagiadakis <[email protected]>	http://anonscm.debian.org/gitweb/ (users/gkiagia-guest/telepathy-kde* repos)
Ubuntu	Michał Zając <[email protected]>	Source: same as debian Binaries: https://launchpad.net/~telepathy-kde/+archive/ppa (stable) Binaries: https://launchpad.net/~telepathy-kde/+archive/daily-builds (latest)
openSUSE	Christophe Giboudeaux (krop on irc #opensuse-kde)	http://download.opensuse.org/repositories/KDE:/Unstable:/Playground/
Arch Linux	Andrea Scarpino (bash) <[email protected]>	https://www.archlinux.org/groups/x86_64/telepathy-kde/
Gentoo	KDE Herd <[email protected]>	http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git

@@ Line 6: / Line 6: @@
 * [http://telepathy.freedesktop.org/releases/telepathy-mission-control/ telepathy-mission-control] >= 5.7.9 (Runtime Dependency)
-We're also using some bits from kdelibs 4.7.0 (Build and Runtime Dependency).
+We're also using some bits from '''kdelibs 4.7.0''' (Build and Runtime Dependency).
 The IM networks that KDE-Telepathy can connect to are decided by which Telepathy Connection Managers are installed. These are runtime only dependencies, but which ones are installed will decide what IM networks KDE-Telepathy supports. The following are the ones we recommend - whether they are installed optionally or required is, of course, up to you.