Major changes in 2.16.0 were:
* Fix input method handling in EelEditableLabel
* Fix build with EEL_OMIT_SELF_CHECK
* Fix crash on DnD from firefox in nautilus
Major changes in 2.15.92 were:
* Translation updates
* Fix intltool build requirement
Major changes in 2.15.91 were:
* Check mtime on background image changes
* Some code cleanups
Major changes in 2.15.90 were:
* Translation updates
* Build fix
Major changes in 2.15.4 were:
* Fix crash in open with dialog
* Fix a11y relation setup
* Wrap long filenames in application selection
Major changes in 2.15.2 were:
* Removal of unused/deprecated code
Major changes in 2.15.1 were:
* New po/LINGUAS support
* Translation fixes
* Correct typo in function name
* Remove obsolete functions
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).
Major changes in 2.14.0 were:
* Translation updates
* Fix a11y crash
Major changes in 2.13.92 were:
* Translation fixes for EditableLabel context menu
* Build fixes
Major changes in 2.13.91 were:
* Fix exec line for open-with desktop files
* Translation updates
Major changes in 2.13.90 were:
* Translation updates.
Major changes in 2.13.4 were:
* New background setting mode supported
* Add eel_mime_get_availible_mime_types()
* HIG fixes to open with dialog
* Don't show alerts in taskbar
Major changes in 2.13.3 were:
* Remove titles from alerts
* Use GtkComboBox instead of (deprecated) GtkOptionMenu
Major changes in 2.13.2 were:
* Fix translations in alerts
* Code cleanups
Major changes in 2.13.1 were:
* sort by name in application chooser
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.
Major changes in 2.12.1 were:
* Translation updates
* Minor code cleanups
Major changes in 2.12.0 were:
* Translation updates
Major changes in 2.11.92 were:
* Translation updates
Major changes in 2.11.91 were:
* Fix scrolling in eel-wrap-table
* Cleanup logging code
Major changes in 2.11.90 were:
* Add x-nautilus-search URI
* Fix wrapping in eel-wrap-table
Major changes in 2.11.4 were:
* Fix memleak
Major changes in 2.11.3 were:
* Fix memleaks
* Fix compiler warnings for gcc 4
Major changes in 2.11.2 were:
* Fix memleaks
Major changes in 2.11.1 were:
* Use new libgnome-menu api
* Fixed crash with accessibility
* Use gmodule-no-export to avoid --export-dynamic
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.
Major changes in 2.10.0 were:
* translation updates
Major changes in 2.9.92 were:
* Application chooser handles case with no existing applications better
* Use automake 1.7
* Fix tests on 64bit systems
* translation updates
Major changes in 2.9.91 were:
* fix crashes in open with dialog
* translation updates
Major changes in 2.9.90 were:
* Show existing applications in open with dialog
* Show icon in application chooser
Major changes in 2.9.2 were:
* Not using deprecated mime apis
* Translation updates
* Function to find out filename encoding
* Fix to eelcanvas that allows connecting to expose
* Handle null mimetypes in property page
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".
Major changes since 2.7.92 were:
* Refresh mime application chooser when mime db changes
* Create ~/.local/share/applications as needed
* Remove some mime-related debug output
Major changes since 2.7.4 were:
* Don't pop up cancel dialog if password dialog is visible.
Major changes since 2.7.3 were:
* Import new foocanvas
* Use right i18n header
* Fix memleaks
* Translation updates
Major changes since 2.7.2 were:
* MIME helpers functions and dialogs
Major changes since 2.7.1 were:
* Translation updates.
Major changes since 2.5.91.1 were:
* Translation updates.
Major changes since 2.5.91 were:
* fix utf8 bug in EelEditableLabel
Major changes since 2.5.90 were:
* translations
Major changes since 2.5.8 were:
* Replaced egg-screen-exec usage with g_spawn
* Use new file chooser
* portability patches
Major changes since 2.5.7 were:
* Translations
Major changes since 2.5.6 were:
* Support for SUS modifiers in eel_strdup_strftime
* Set right a11y role on alerts
Major changes since 2.5.5 were:
* Fix a11y coloring of editable label
* Canvas update
Major changes since 2.5.4 were:
* Removed unused source files
* Added a GList API for string lists in eel-preferences.
Major changes since 2.5.3 were:
* HIG message dialogs
Major changes since 2.5.2 were:
* Mem leak fix in accessibility support.
Major changes since 2.5.1 were:
* Added accessibility support to editable label widget
Major changes since 2.5.0 were:
* Some ICCCM fixes
* disable deprecation warnings
* fix leaks
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.