around at either build-time or at run-time is:
USE_TOOLS+= perl # build-time
USE_TOOLS+= perl:run # run-time
Also remove some places where perl5/buildlink3.mk was being included
by a package Makefile, but all that the package wanted was the Perl
executable.
by other package Makefiles, and with the deprecation of USE_BUILDLINK3
support in the infrastructure files, these had the potential to break
existing packages.
2.10.0
======
Translators
- Ivar Smolin (et)
- Žygimantas Beručka (lt)
- Reinout van Schouwen (nl)
- Mişu Moldovan (ro)
- Maxim Dziumanenko (uk)
- Canonical Ltd (xh)
2.9.90
======
Fixes
- Fix daemon reloading causing listeners to break (Mark)
- Fixes problem where a path file which only includes another path
file wouldn't work (Mark)
- Fix double free with gconf_client_clear_cache() (Mark)
- Add pre-condition to gconf_value_validate (Vincent Untz)
Translators
- Rostislav Raykov (bg)
- Priit Laes (et)
- Pauli Virtanen (fi)
- Marcel Telka (sk)
2.9.2
=====
Fixes
- Make all_entries() get the schema name when the value is set
(Fernando Herrera)
- Look up value in the C locale even if its found in the current locale
(Fernando Herrera)
- Add title/name to the API documentation (Jonathan Blandford)
Translators
- Changwoo Ryu (ko)
Fixes
- If the toplevel directory of a source isn't writable, then mark the
whole source as readonly (Mark)
- Plug various leaks (Kjartan)
Translators
- Christophe Merlet (RedFox) (fr)
- Alessio Frusciante (it)
- Žygimantas Beručka (lt)
- Li-Jen Hsin (zh_TW)
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".
Fixes:
- Get rid of duplicate '/' with AM_GCONF_SOURCE_2 (Daniel Elstner)
- Don't create a directory for docs if we're not installing them (Julio M.
Merino Vidal)
- Fix a bug with the markup backend on 64-bit (Joe Marcus Clarke)
- Fix a leak (Kjartan)
- Return an error for incorrect source addresses (Mark)
Translators:
- Gisela Carbonell (ca)
- Christian Neumair (de)
- Christophe Merlet (RedFox) (fr)
- LoneStar (zh_CN)
Fixes:
- add a --enable-gtk=yes/no/auto configure arg (Julio Merino, Mark)
- fix basic example app to not crash (Elijah Newren)
- don't try and create a dir if it already exists (Ryan Lovett, Mark)
- only ever create the $(HOME)/.gconfd/ dir in the daemon (Colin Walters)
- add quotes around AM_GCONF_SOURCE_2 (Frédéric L. W. Meunier)
- handle <entry> with only <schema_name> correctly in --load (Mark)
- fix the order in which local-defaults.path gets included (Mark)
- fix minor inefficiency when not printing debugging messages (Mark)
Translators:
- Adam Weinberger (en_CA)
- Robert Sedak (hr)
- Samúel Jón Gunnarsson (is)
- Alessio Frusciante (it)
- Takeshi AIHANA (ja)
- Amanpreet Singh Alam (pa)
- Gurkan Aslan (tr)
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.
one or more .entries files, it can set GCONF2_ENTRIES to the names of those
files and they will get (un)registered at (de)installation time.
Installation is handled after .schemas are installed, and uninstallation
before .schemas are deinstalled.
To achieve this, we need to implement an --unload flag in gconftool-2 to
allow clean removal of .entries from the database. This will be fed back
to authors.
Bump PKGREVISION to 1.
2.4.0
- print usage message when no options passed to gconftool
- API docs updates
- fix UTF-8 handling for command line output
- fix reliability of writing out XML
- ensure recursive unsets get synced
- fix flag value that was "0"
- fix recursive preloading
- fix a memleak
- fix some gconftool messages/segfaults
2.3.3
- new gconf_client_notify() API to fake a notification
- fixes to gconftool --dump feature
- implement schema uninstallation in gconftool so packages
can avoid leaving junk
- fix build issues with linc-free ORBit
- new gconf_client_recursive_unset API
- fix gcc 3.3 strict aliasing warnings
2.3.2
- fix build on Cygwin
- don't complain about missing saved_state in syslog
- improve gconf-sanity-check error text
- added --get-type, --get-list-size and --get-list-element
- exported gconf_entry_copy
- cleaned up headers for C++
- added missing GCONF_CLIENT_GET_CLASS
- hackaround fix for 2.3.1 lockfile breakage
