summaryrefslogtreecommitdiff
path: root/chat/telepathy-mission-control
AgeCommit message (Collapse)AuthorFilesLines
2011-11-01Recursive bump for graphics/freetype2 buildlink addition.sbd2-4/+4
2011-04-22recursive bump from gettext-lib shlib bump.obache2-4/+4
2011-01-13png shlib name changed for png>=1.5.0, so bump PKGREVISIONs.wiz2-4/+4
2010-11-15PKGREVISION bumps for changes to gtk2, librsvg, libbonobo and libgnomeabs2-4/+4
2010-09-14Bump dependency on pixman to 0.18.4 because cairo-1.10 needs thatwiz2-4/+4
version, and bump all depends. Per discussion on pkgsrc-changes.
2010-06-13Bump PKGREVISION for libpng shlib name change.wiz2-4/+4
Also add some patches to remove use of deprecated symbols and fix other problems when looking for or compiling against libpng-1.4.x.
2010-02-10Bump revision for PYTHON_VERSION_DEFAULT change.joerg1-2/+2
2009-08-29marked as user-destdir support.obache1-1/+3
2009-08-26bump revision because of graphics/jpeg updatesno2-3/+4
2009-06-14Convert @exec/@unexec to @pkgdir or drop it.joerg1-3/+2
2009-06-14Remove @dirrm entries from PLISTsjoerg1-10/+1
2009-04-01We need to tell configure which python binary to use.roy1-1/+4
2009-03-20Simply and speed up buildlink3.mk files and processing.joerg1-13/+6
This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-02-09Switch to Python 2.5 as default. Bump revision of all packages that havejoerg1-1/+2
changed runtime dependencies now.
2008-11-14Initial import of telepathy-mission-control-4.67:wiz6-0/+204
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.