rra-c-util 3.7

There are a surprisingly large variety of changes in this release. I keep expecting this package to stabilize, but I keep finding new bits of shared infrastructure that it's good to maintain in a single location.

The main new code in this release is an import of the generic buffer library that I expanded for INN from some code that was already there. This is a set of functions for managing a buffer that holds some amount of allocated memory along with counts of contents used and available. It's useful for processing data received from the network or other cases where one wants automatic resizing of buffers. I thought I was going to use this for another project (but ended up not doing so) and had been meaning to incorporate it for a while, since I know there are some packages that I haven't yet converted to my infrastructure that will benefit from it.

Also new in this release are Autoconf macros for detecting APR and APR-Util, which are being used by my current project.

The PAM utility library's configuration handling now copes properly (at least as much as it can) when krb5_appdefault_string is a stub that does nothing, which is the case in Mac OS X 10.7. The PAM configure support also now correctly detects that FreeBSD's PAM API uses const.

The kafs configure macros now abort if the platform requires OpenAFS headers and those headers aren't found, and the kafs code is not built in rra-c-util itself by default (since having OpenAFS installed is relatively rare).

Other minor changes: include strings.h in portable/system.h for strncasecmp, add ARRAY_SIZE and ARRAY_END macros to util/macros.h, prefer gssapi/gssapi.h to gssapi.h since the former is deprecated on FreeBSD, and fix a compiler warning in util/messages.c.

I've also gone through all files meant to be copied into other source packages and added a comment saying that the file is maintained in rra-c-util and giving a pointer to its web site.

You can get the latest version from the rra-c-util distribution page.

Posted: 2011-07-25 18:40 — Why no comments?

Last spun 2022-02-06 from thread modified 2013-01-04