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.
--------------------------------------------------------------------------
pilot-link 0.12.2, "Dance With the Devil" aka "Distraction", 02-09-2007
--------------------------------------------------------------------------
5 months since the last release (0.12.1) and we have another release! This
one is mostly a maintenance release, but there are some new things in here.
Major Features:
* More cleanup in libpisock and documentation, addition of some new
(working :) BlueZ support, new udev rules, expanded OS5 Contacts
support, expanded OS X support and a lot more!
Other Features:
* No major features in this release, mostly bug fixes and minor
tweaks here and there. The website has also been refreshed with
new content and a completely new layout. All source files are now
version-tracked in the header.
Bug Fixes:
* Python support was broken, fixed now, doh! Palm T|X over libusb
has been fixed (we hope) with this release. Of course we need
testers to validate that. All of userland is renamed now to avoid
some namespace pollution. Documentation is all current with
respect to this release, all manpages are in XML source format
(requires xsltproc to process), and much more.
pilot-link v0.12.1
There isn't much "new" in this release, just some rapid-fire bug fixes
reported from users and a lot of code has been cleaned up in the tree
to remove unnecessary includes.
* Code cleanup in libpisock, libpisync, src and include
* Fixed the installation faux pas with udev rules, oops!
pilot-link v0.12.0
pilot-link 0.12.0 "Trois ans" ("Three Years") is now official.
There have been so many changes in this release and I can't remember
them all, but here's the short list:
* Many of the userland binaries now have new names, to avoid some
potential namespace collisions (dlpsh is now pilot-dlpsh for example,
memos is now pilot-memos). If you use scripts which call these
applications, you may have to make minor changes to accomodate the
new naming scheme.
* Documentation is now in DocBook XML, and manpages are dynamically
generated from that source. Other docs are much more detailed, and
there are quite a few README files that have been added to help.
* Direct libusb support! This is one of the most monumental features in
0.12.0, and should help those who have trouble using the kernel's
visor driver in Linux with their device. Now you can get a healthy
300% to 600% speedup in sync times, depending on your Palm's
processor speed. See doc/README.libusb for details. Thanks go to
Zephania Hull for working out how to get native libusb working with
pilot-link.
* Native support for Mac OS X. You can now just download the tarball
and build it directly on Mac OS X machines, and it will just run.
Thanks go to Florent Pillet for his tireless work in getting this all
working efficiently and for squashing countless bugs in the libraries
along the way.
* So many other fixes, additions, features and new things to count.
and add a new helper target and script, "show-buildlink3", that outputs
a listing of the buildlink3.mk files included as well as the depth at
which they are included.
For example, "make show-buildlink3" in fonts/Xft2 displays:
zlib
fontconfig
iconv
zlib
freetype2
expat
freetype2
Xrender
renderproto
RECOMMENDED is removed. It becomes ABI_DEPENDS.
BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.
BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.
BUILDLINK_DEPENDS does not change.
IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".
Added to obsolete.mk checking for IGNORE_RECOMMENDED.
I did not manually go through and fix any aesthetic tab/spacing issues.
I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.
I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.
As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.
As discussed on tech-pkg.
I will commit to revbump, pkglint, pkg_install, createbuildlink separately.
Note that if you use wip, it will fail! I will commit to pkgsrc-wip
later (within day).
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.
NetBSD and Linux). On a non-NetBSD sysrtem, kdepim3 failed to
build because was missing libncurses.la file.
I did not bump any PKGREVISIONs, because under my tests either
it worked fine before, because libcurses was part of base OS,
or the packages didn't build in the first place.
pkgsrc. Instead, a new variable PKGREVISION is invented that can get
bumped independent of DISTNAME and PKGNAME.
Example #1:
DISTNAME= foo-X.Y
PKGREVISION= Z
=> PKGNAME= foo-X.YnbZ
Example #2:
DISTNAME= barthing-X.Y
PKGNAME= bar-X.Y
PKGREVISION= Z
=> PKGNAME= bar=X.YnbZ (!)
On subsequent changes, only PKGREVISION needs to be bumped, no more risk
of getting DISTNAME changed accidentally.
BUILDLINK_PREFIX.<pkgname>. This allows buildlink to find X11BASE packages
regardless of whether they were installed before or after xpkgwedge was
installed. Idea by Alistair Crooks <agc@pkgsrc.org>.
pilot-link-libs depend on this most recent version (0.9.5). Conveniently,
all the packages using buildlink.mk files have dependencies automatically
updated by modifying this one location.
