thrulay-0.8 release notes
Linux compatibility release; fixes problems with compiling the
software on some flavors of Linux.
thrulay-0.7 release notes
This release incorporates the results of the work of Bernhard Lutzmann
on his Google Summer of Code project.
since they always need a C compiler, even when the source code is
completely in C++.
For some other packages, stated in the comment that a C compiler is
really not needed.
had actually been ignoring LTCONFIG_OVERRIDE anyway and just using
the default LIBTOOL_OVERRIDE to replace libtool scripts in packages.
This just formalizes the fact that LTCONFIG_OVERRIDE is not used
meaningfully by pkgsrc.
* Change the default pattern. Samba is trying to cheat by
special casing IOZONE.tmp, and the pattern of 0xA5.
* Make the default pattern random, and based on Iozone version.
This is to prevent the hack from Richard Sharpe (in Samba)
from special casing Iozone, and lying to the user.
* bug fix in pattern gen.
* Add -+Z old data set mode.
* Add -+X constant data for short circuit testing only.
* Multi-node changes for new options. (-+Z and -+X)
* Add -+K flag for Sony.
* Move -+K outside of Windows only.
* Simplify percentage calculation
* Add error checking for -f and -F in the wrong modes.
* Bug fix for pbuffer allocation on remote clients.
* Check for max_rec_size when using ranges. -r -r -r
* Fix for Debian user bug. -r 1m -n 1m -g 2m gave bogus error.
* Bug fix for -k used in conjunction with -t and content validation.
Bump PKGREVISION.
Remove the INSTALLATION_DIRS that was there because
1.03a precreates all these anyways.
todo: patch bonnie++.8 to point to correct path to readme.html
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.
"extract" script for extraction. Many cases where a custom EXTRACT_CMD
simply copied the distfile into the work directory are no longer
needed. The extract script also hides differences between pax and
tar behind a common command-line interface, so we no longer need code
that's conditional on whether EXTRACT_USING is tar or pax.
