file's sole purpose was to provide a dependency on pkg-config and set
some environment variables. Instead, turn pkg-config into a "tool"
in the tools framework, where the pkg-config wrapper automatically
adds PKG_CONFIG_LIBDIR to the environment before invoking the real
pkg-config.
For all package Makefiles that included pkg-config/buildlink3.mk, remove
that inclusion and replace it with USE_TOOLS+=pkg-config.
and koffice build.
And do in meta-pkgs/kde3/kde3.mk as suggested by maintainer, markd.
It helps with builds on Linux for kdegraphics3, libkipi, gwenview,
kdelibs3, kdebase3, arts, and many other KDE-based packages on Linux.
(It was not needed for kile, but will be used.)
Thank you, Torsten Harenberg for testing many packages such as
kdenetwork, kdegames, kdepim, kdemultimedia.
I still don't know what the correct fix is for PR #25402.
arts fails to build under Linux with many lines like:
.libs/kmedia2.o(.gnu.linkonce.d._ZTIN4Arts20VideoPlayObject_baseE+0x10):../mcop/common.h:72: undefined reference to `typeinfo for Arts::Object_base'
Use BUILDLINK_TRANSFORM to remove
-Wl,--allow-shlib-undefined
-Wl,--no-undefined
(Note that KDE packages still have same problem.)
with:
@unexec ${RMDIR} %D/include/arts 2>/dev/null || ${TRUE}
This will stop it from complaining when you use pkg_add to
upgrade the arts package when kdelibs is still installed.
Okayed by maintainer, markd.
Highlights at a glance
* Text-to-speech system with support built into Konqueror, Kate, KPDF
and the standalone application KSayIt
* Support for text to speech synthesis is integrated with the desktop
* Completely redesigned, more flexible trash system
* Kicker with improved look and feel
* KPDF now enables you to select, copy & paste text and images from
PDFs, along with many other improvements
* Kontact supports now various groupware servers, including eGroupware,
GroupWise, Kolab, OpenGroupware.org and SLOX
* Kopete supports Novell Groupwise and Lotus Sametime and gets
integrated into Kontact
* DBUS/HAL support allows to keep dynamic device icons in media:/ and
on the desktop in sync with the state of all devices
* KHTML has improved standard support and now close to full support for
CSS 2.1 and the CSS 3 Selectors module
* Better synchronization between 2 PCs
* A new high contrast style and a complete monochrome icon set
* An icon effect to paint all icons in two chosen colors, converting
third party application icons into high contrast monochrome icons
* Akregator allows you to read news from your favourite RSS-enabled
websites in one application
* Juk has now an album cover management via Google Image Search
* KMail now stores passwords securely with KWallet
* SVG files can now be used as wallpapers
* KHTML plug-ins are now configurable, so the user can selectively
disable ones that are not used. This does not include Netscape-style
plug-ins. Netscape plug-in in CPU usage can be manually lowered, and
plug-ins are more stable.
* more than 6,500 bugs have been fixed
* more than 1,700 wishes have been fullfilled
* more than 80,000 contributions with several million lines of code and
documentation added or changed
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:
lib/libfoo.a
lib/libfoo.la
lib/libfoo.so
lib/libfoo.so.0
lib/libfoo.so.0.1
one simply needs:
lib/libfoo.la
and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.
Also make LIBTOOLIZE_PLIST default to "yes".
by moving the inclusion of buildlink3.mk files outside of the protected
region. This bug would be seen by users that have set PREFER_PKGSRC
or PREFER_NATIVE to non-default values.
BUILDLINK_PACKAGES should be ordered so that for any package in the
list, that package doesn't depend on any packages to the left of it
in the list. This ordering property is used to check for builtin
packages in the correct order. The problem was that including a
buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed
from BUILDLINK_PACKAGES and appended to the end. However, since the
inclusion of any other buildlink3.mk files within that buildlink3.mk
was in a region that was protected against multiple inclusion, those
dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
the normal case when BUILDLINK_DEPENDS.<pkg> isn't specified, it receives
a value only once due to the multiple inclusion protection in the
bulldlink3.mk files. In the case where a package includes several
buildlink3.mk files that each want a slightly different version of another
dependency, having BUILDLINK_DEPENDS.<pkg> be a list allows for the
strictest <pkg> dependency to be matched.
