A build fix applied upstream some ten years ago for Mac OS X is only
really relevant for that OS, and was causing build breakages on NetBSD
with any archs that didn't happen to be covered in legacy code in
arpa/nameser_compat.h. (Encountered with powerpc, would also presumably
break others, like aarch64.) No PKGREVISION, build fix only.
The actual fix as been done by "pkglint -F */*/buildlink3.mk", and was
reviewed manually.
There are some .include lines that still are indented with zero spaces
although the surrounding .if is indented. This is existing practice.
Many of these definitely do not depend on readline.
So there must be a different underlying problem, and that
should be tracked down instead of papering over it.
Solves:
/usr/libexec/binutils225/elf/ld.gold: error: cannot find -lreadline
The missing specification is obvious on DragonFly because there's
no publically accessible version of readline in base.
There have been many changes since the previous official release, 1.4.3, which
was published 7 years ago, so we'll only mention a few of them:
- This Loudmouth release is compatible with current Glib/GTK libraries
- The internal asyncns copy has been removed
- The security has been improved in several ways:
- Certificates: added checking of SAN(s) when CN does not match and fixed CN
wildcard handling
- SSL 2 and 3 have been deactivated; TLS 1.1 and 1.2 have been activated
- Use the default cipher suite of GnuTLS
- New API: Implementation of lm_ssl_set_ca and lm_ssl_set_cipher_list
This enables the application to choose additional CA certificates to trust
as well as the cipher suites which are used by OpenSSL or GnuTLS
- Many resolver and parser issues have been fixed
I can't find a subsequent changelog for 1.5.1 to 1.5.3 but assume "bugs fixed".
Problems found with existing distfiles:
distfiles/icb-5.0.9.tar.gz
distfiles/icb.2.1.4.tar.Z
distfiles/zenicb-19981202.tar.gz
No changes made to these /distinfo files.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
* Install a dummy log handler to avoid spamming e.g. the irssi-xmpp console
window in non-debug mode, patch from:
65fda2c884
* Fix build on Darwin
* Add patch comments and LICENSE.
Bump PKGREVISION.
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.
Fixed issues in Loudmouth 1.4.3
* [#19] - Uses old style auth if server provides old style auth and SASL
* [#22] - Handlers which were registered for message ids should always be called if the id matches
* [#23] - Receiving messages larger than 1023 bytes are not fully processed with OpenSSL backend
* [#27] - Functions missing in docs from LmSSL
Loudmouth 1.4.1
Loudmouth 1.4.1 contains a bugfix from 1.4.0 causing some clients to be disconnected if connected through a NAT firewall.
Loudmouth 1.4.0 contains no changes from 1.3.4 but is simply a release to mark it as the new stable branch.
Loudmouth 1.3.4
Loudmouth 1.3.4 is a release on the unstable 1.3 branch. It contains of added
features and bug fixes.
Loudmouth 1.3.3 released
Loudmouth 1.3.3 is a release on the unstable 1.3 branch. It contains of added
features and bug fixes.
Loudmouth 1.3.2 released
Loudmouth 1.3.2 is a release on the unstable 1.3 branch. It contains of added
features and bug fixes.
* This is the same as 1.1.5 but marked as stable and released as 1.2.0.
* For a complete list of changes since 1.0.5 look at the changes in 1.1.1-1.1.5
Changes 1.1.5:
* Fixed leak when closing a connection, LM-59
* Escape the resource string (fixes problems with iChat contacts), LM-48
* Stale incoming source destroyed/unreffed, LM-60
* Fixed a leak in the synchronous layer, LM-66
* Fixed a couple of warning when building on 64 bit alpha, LM-41.
Changes 1.1.4:
* Generate better message IDs, LM-56
* Fixed a leaking proxy object, LM-51
* Fixed random bugs on connection errors, LM-58
* Removed a warning when using proxy, LM-50.
* Fixed issue where no disconnect signal was emitted when connection closed
during opening
* Plugged a memory leak in LmConnection
* Fixed warnings due to uninitialized value
* Fixed a reentrancy-related issue with LmConnection
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
* Quick build fix release when building without SSL, LM-25.
Changes 1.0.2:
* Fixed issue when opening in blocking mode failed, LM-15
* Unregister sources when connection fails to avoid later segfault, LM-16
* Fixed an issue where large messages would get trunkated, LM-17
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).
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.
Changes in 1.0:
---------------
* Fix crash when connection goes down using SSL, LM-3 (Mikael Hallendal)
* Fixed some GCC 4.0 warnings (Mikael Hallendal)
* Some API fixups for consistency in LmSLL (Mikael Hallendal)
* Don't try to setup SSL if it's not supported (Martyn Russel)
* Documentation fixes (Mikael Hallendal)
* State fixes when using blocking API, LM-7 (Mikael Hallendal)
* Check that connection is open before using it, LM-6 (Mikael Hallendal)
* Fix infinite loop in blocking open if failed, LM-8 (Mikael Hallendal)
Changes in 0.90:
----------------
* Two crashers for ssl read fixed (Micke, Daniel Lavalliere)
* Fixed a couple of leaks when freeing the connection (Daniel Lavalliere)
* A couple of thread related issues solved (Micke, Daniel Lavalliere)
* Work with latest GnuTLS (foser)
* Improved the example tools some (Micke)
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.
