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).
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.
libglade-2.5.1: 11-February-2005
- Fix toolbar breakage from the 2.4.1/2.5.0 releases.
- Fix handling of GtkFileChooserDialog internal children.
libglade-2.5.0: 29-November-2004
- Add support for GtkFileChooserButton, GtkIconView,
GtkAboutDialog and GtkMenuToolButton.
- Register GtkFileChooserDialog correctly.
- Fix a number of bugs in the libglade-convert utility.
- Fix some memory leaks in the XML parsing code.
- Handle tooltips on GtkToolItems properly, and get rid of uses of
the old toolbar API.
- Fix some bugs in setting up ATK relations.
- Various other bug fixes (see ChangeLog).
script, but as the package is currently missing another dependency, it's not
being installed.
Therefore, and as we haven't noticed any other package requiring this utility,
simply drop it completely. (If it's needed some day, we can simply create a
package to install it, but depending on python here is not good.)
Bump PKGREVISION to 1.
- Register GtkFileChooserDialog correctly.
- Fix a number of bugs in the libglade-convert utility.
- Fix some memory leaks in the XML parsing code.
- Handle tooltips on GtkToolItems properly, and get rid of uses of
the old toolbar API.
- Fix some bugs in setting up ATK relations.
- Various other bug fixes (see ChangeLog).
The BUILD_DEPENDS dates back to September and so
libglade shared libraries from then need old (no longer existing)
libxml, pango, and gtk2 libraries.
I noticed this when installing packages on a machine that already had
the (what it thought was) correct dependencies.
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".
libglade-2.3.6: 10-March-2004
- Implement support GtkComboBoxEntry, GtkToolItem, GtkToolButton,
GtkToggleToolButton, GtkRadioToolButton & GtkSeparatorToolItem (Damon
Chaplin)
- Fix automake warning (Steve Chaplin)
- Add libglade version number to the docs (Matthias Clasen)
- Fix usage of C++ keyword as an argument name (Bas Driessen)
- Allow additional signal parameter for glademm (Christof Petig)
- Support tooltips in toolbars (Michael Voigt)
libglade-2.3.2: 15-January-2004
- Support disambiguating msgids by prefixing them with a context
string. (Christian Stimming, Matthias Clasen)
libglade-2.3.1: 14-November-2003
- Register GtkColorButton, GtkComboBox, GtkFileChooser and
GtkFontButton types (Jonathan Blandford)
- Implemement support for GtkExpander (Mark McLoughlin)
- Fix memory leak and incorrect colour map usage (Morten Welinder)
- Win32 build support (Tor Lillqvist, Masahiro Sakai)
- Build fixes (James Henstridge, Michael Meeks)
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.
