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.
This switches to the new gnome-2.20 branch.
Also add the Python bindings as a seperate pkg. I don't see where
this is used, but is is a simple addition.
or USE_X11BASE set, but don't include mk/x11.buildlink3.mk directly or
via buildlink3.mks
- introduce BUILDLINK_PREFIX.libXpm as alias for BUILDLINK_PREFIX.xpm
in the !modular case
- fix some cases where the check for libX11 couldn't work at all by using
C++ for compilation without including the proper headers
Verified using a full X11_TYPE=xorg bulk build without additional
breakage. Discussed with salo@, wiz@ and send to packages@ for feedback.
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
PKGLOCALEDIR and which install their locale files directly under
${PREFIX}/${PKGLOCALEDIR} and sort the PLIST file entries. From now
on, pkgsrc/mk/plist/plist-locale.awk will automatically handle
transforming the PLIST to refer to the correct locale directory.
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).
What's new in at-spi-1.7.4:
* Fixed dist to include Accessibility_Selector.idl (missing from dist though
in cvs since 1.7.3).
* Bugfixes to EventDetails event support, and fixed event emission for
implementors of SPI_REMOTE_OBJECT.
What's new in at-spi-1.7.0 through 1.7.3:
* Added idl/Accessibility_Selector.idl to the repository (missing in 1.7.0
through 1.7.2, added in 1.7.3)
* DOCS:
All the IDL is now documented with doxygen-compatible docs.
Just run 'doxygen oxyfile' in the IDL directory. (This will
be automated in a future version).
* NEW API:
idl:
Accessibility::Accessible:getAttributes (name/value pair annotation
for all objects)
Accessibility::Accessible:getApplication (retrieves ref to host app)
Accessibility::Component:getAlpha (get transparency/opacity value of component)
Accessibility::Image:getLocale (get POSIX locale for image and
imagedesc)
Accessibility::Text:getAttributeValue (retrieve a single named
attribute value)
Accessibility::Relation:RELATION_PARENT_WINDOW_OF
Accessibility::Role:ROLE_ENTRY, ROLE_CHART, ROLE_CAPTION,
ROLE_DOCUMENT_FRAME, ROLE_HEADING, ROLE_PAGE, ROLE_SECTION (New roles
for complex docs and forms.)
Accessibility::State:STATE_REQUIRED, STATE_TRUNCATED, STATE_ANIMATED,
STATE_INVALID_ENTRY, STATE_SUPPORTS_AUTOCOMPLETION,
STATE_SELECTABLE_TEXT, STATE_IS_DEFAULT (New states, for complex forms)
Accessibility::EventDetails (new, more detailed info marshalled with events)
cspi:
(AccessibleEvent_getSourceName):
(AccessibleEvent_getSourceRole):
(AccessibleEvent_getSourceApplication):
(AccessibleEvent_getSourceDetails):
New methods for interrogating/demarshalling
event details i.e. source's accessible name, role,
and host app.
(Accessible_getAttributes): New, retrieve annotations/attributes
on objects.
(Accessible_getHostApplication): New, retrieve enclosing Application
instance for an object.
(AccessibleImage_getImageLocale): New, retrieve Locale info for an
image.
(AccessibleComponent_getAlpha): New, retrieve alpha value for
an AccessibleComponent (see discussion in idl section above).
* BUGFIXES:
Some compiler fixes from Kjartan Marass.
Some thread-related fixes from Michael Meeks.
Don't allow non-preemptive listeners to pre-empt events! (Bill Haneman).
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
* Fixed some discrepancies in event listener deregistration, improves
on-the-fly deregistration of event listeners. Fixed some tests.
* Added cspi docs back into dist.
* Fixed brokenness in 'make check.'
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.
Several changes are involved since they are all interrelated. These
changes affect about 1000 files.
The first major change is rewriting bsd.builtin.mk as well as all of
the builtin.mk files to follow the new example in bsd.builtin.mk.
The loop to include all of the builtin.mk files needed by the package
is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk
is now included by each of the individual builtin.mk files and provides
some common logic for all of the builtin.mk files. Currently, this
includes the computation for whether the native or pkgsrc version of
the package is preferred. This causes USE_BUILTIN.* to be correctly
set when one builtin.mk file includes another.
The second major change is teach the builtin.mk files to consider
files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most
of the builtin.mk files test for the presence of built-in software by
checking for the existence of certain files, e.g. <pthread.h>, and we
now assume that if that file is under ${LOCALBASE}, then it must be
from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The
exceptions to this new check are the X11 distribution packages, which
are handled specially as noted below.
The third major change is providing builtin.mk and version.mk files
for each of the X11 distribution packages in pkgsrc. The builtin.mk
file can detect whether the native X11 distribution is the same as
the one provided by pkgsrc, and the version.mk file computes the
version of the X11 distribution package, whether it's built-in or not.
The fourth major change is that the buildlink3.mk files for X11 packages
that install parts which are part of X11 distribution packages, e.g.
Xpm, Xcursor, etc., now use imake to query the X11 distribution for
whether the software is already provided by the X11 distribution.
This is more accurate than grepping for a symbol name in the imake
config files. Using imake required sprinkling various builtin-imake.mk
helper files into pkgsrc directories. These files are used as input
to imake since imake can't use stdin for that purpose.
The fifth major change is in how packages note that they use X11.
Instead of setting USE_X11, package Makefiles should now include
x11.buildlink3.mk instead. This causes the X11 package buildlink3
and builtin logic to be executed at the correct place for buildlink3.mk
and builtin.mk files that previously set USE_X11, and fixes packages
that relied on buildlink3.mk files to implicitly note that X11 is
needed. Package buildlink3.mk should also include x11.buildlink3.mk
when linking against the package libraries requires also linking
against the X11 libraries. Where it was obvious, redundant inclusions
of x11.buildlink3.mk have been removed.
* LoginHelper API docs improved.
* fixed bug which caused problems if an app which loaded atk-bridge forks,
and one fork exits. (Padraig O'Briain).
* New language: Galician (gl), Jesus Bravo Alvarez.
* Ansi build fixes (Kjartan Maraas).
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".
What's new in at-spi-1.6.0:
Nothing.
What's new in at-spi-1.5.4:
* Registration failure at SPI_init is now detected and
an error code is returned to the caller (bug #147648).
* We now use polling as our default for detecting mouse
button changes (this was formerly our fallback method);
this prevents conflict with Xstroke.
[a better long-term fix requires the Xevie extension]
* We now register on a per-DISPLAY, but not per-SCREEN, basis.
This fixes several issues, see bugs #149962, #136986, #144086.
* New languages in configure.in:
bs (Christian Rose)
nb (Kjartan Maraas)
============
What's new in at-spi-1.5.3:
* New role EMBEDDED (bug #144415).
* Added object:bounds-changed event, for detecting when the
component bounds of an object have changed onscreen.
==============
What's new in at-spi-1.5.2:
* Added Accessibility_LoginHelper interface, and
LoginHelper GType. Also added client and server tests
for this interface. The purpose is to identify services
(typically, assistive technologies) which need access to
system or device services (keyboard, audio, serial ports,
posting windows, etc.) during login or re-login/authentication.
* fixed make distcheck.
* Added a check in cspi_object_unref, which should help in detecting
refcount bugs in clients (Padraig O'Briain).
* New languages:
Walloon (Pablo Saratxaga)
Bulgarian (Alexander Shopov)
What's new in at-spi-1.5.1:
* Allow synthesis of keysyms that aren't in the current X keymap.
* languages: Gujarati (Guntupalli Karunakar), Canadian English
(Alexander Winston)
* Added omitted declarations for already-existing methods
AccessibleTable_addRowSelection(),
AccessibleTable_addColumnSelection(),
AccessibleTable_removeRowSelection(),
AccessibleTable_removeColumnSelection().
* bug fixes: 136660, 120659 (partial), 132237, 134332.
What's new in at-spi-1.4.0: [GNOME 2.6.0 release]
* build improvements from Laszlo Peter.
* en_GB added to ALL_LINGUAS.
What's new in at-spi-1.3.16: [GNOME 2.6 RC1 release]
* Fix for bug #134036, which could steal keystrokes from applications
if at-spi registry failed.
* Build fixes, added .pc.in files (from Laszlo Peter).
This is the gnome-2.6 beta release of at-spi.
What's new in at-spi-1.3.15:
* translations:
Amanpreet Singh Alam (pa)
Bojan Suzic (sr@ije)
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.
