summaryrefslogtreecommitdiff
path: root/chat/telepathy-mission-control/distinfo
AgeCommit message (Collapse)AuthorFilesLines
2020-11-21Remove telepathy-mission-control, replaced by telepathy-mission-control5nia1-11/+0
years ago.
2015-11-03Add SHA512 digests for distfiles for chat categoryagc1-1/+2
Problems found with existing distfiles: distfiles/icb-5.0.9.tar.gz distfiles/icb.2.1.4.tar.Z distfiles/zenicb-19981202.tar.gz No changes made to these /distinfo files. Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
2012-10-24Don't define a function inline without providing the implementation.joerg1-1/+3
2012-05-06Build fixes for new glib2.dholland1-1/+3
2008-11-14Initial import of telepathy-mission-control-4.67:wiz1-0/+6
Mission Control, or MC, is a Telepathy component providing a way for "end-user" applications to abstract some of the details of connection managers, to provide a simple way to manipulate a bunch of connection managers at once, and to remove the need to have in each program the account definitions and credentials. Misson Control implements some well-defined API's much like each connection manager respond to a set of well-defined telepathy API's. The set of API's implemented by MCs will be split in several interfaces to ease progressive and adaptative implementation of each facet. There are different types of files that the MC will use, and that are installed by the various connection managers package or third-party application needing to be hooked-in. MC is able to handle all those file formats as expected.