2009-04-01 18:20:41 by Roy Marples | Files touched by this commit (6) |
Log message:
We need to tell configure which python binary to use.
|
2009-03-20 20:25:55 by Joerg Sonnenberger | Files touched by this commit (1252) |
Log message:
Simply and speed up buildlink3.mk files and processing.
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-09 23:56:28 by Joerg Sonnenberger | Files touched by this commit (167) |
Log message:
Switch to Python 2.5 as default. Bump revision of all packages that have
changed runtime dependencies now.
|
2008-11-14 23:58:06 by Thomas Klausner | Files touched by this commit (5) | |
Log message:
Initial import of libtelepathy-0.3.3:
The Telepathy project is building a unified framework for many
different kinds of real-time communications. It uses the D-Bus
messaging system to provide a simple interface for client applications,
allowing them to quickly take advantage of Telepathy's benefits.
* Real-time: Telepathy supports instant messaging (both one-to-one
and in groups), voice calls and video calls; it's less suited for
store-and-forward applications like email
* Unified: Many different programs can take advantage of these
communications; Telepathy lets these programs work together
* Framework: Telepathy allows the different aspects of communication
handling to be divided between different parts of the system,
meaning each part is simpler
|