| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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.
|
|
until proven otherwise.
|
|
either because they themselves are not ready or because a
dependency isn't. This is annotated by
PYTHON_VERSIONS_INCOMPATIBLE= 33 # not yet ported as of x.y.z
or
PYTHON_VERSIONS_INCOMPATIBLE= 33 # py-foo, py-bar
respectively, please use the same style for other packages,
and check during updates.
Use versioned_dependencies.mk where applicable.
Use REPLACE_PYTHON instead of handcoded alternatives, where applicable.
Reorder Makefile sections into standard order, where applicable.
Remove PYTHON_VERSIONS_INCLUDE_3X lines since that will be default
with the next commit.
Whitespace cleanups and other nits corrected, where necessary.
|
|
|
|
|
|
(additionaly, reset PKGREVISION of qt4-* sub packages from base qt4 update)
|
|
|
|
It turns out there were a lot of these.
|
|
|
|
|
|
a) tiff update to 4.0 (shlib major change)
b) glib2 update 2.30.2 (adds libffi dependency to buildlink3.mk)
Enjoy.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
changed runtime dependencies now.
|
|
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
|
