Changes since 1.2.4:
Changes in 1.2.6:
* Fix memory leaks on Windows.
* Correct font size problems.
* Enable missing FLAC support.
Changes in 1.2.5:
* An official Intel Mac version is now available.
* Fixed bug in Generate Silence which caused it to apply to all tracks
instead of just the selected ones.
* Mac OS X: audio device opening code has been rewritten. First, it
is much more conservative about changing device settings; it will
not change settings when you open the program or close the
preferences dialog anymore, and it will not change the settings when
you begin playback/recording if the current settings are adequate.
When it does change the settings, it should work much better on
devices such as the Griffin iMic, ART USB Phono Plus,
and Ion iMX02 USB.
* Mac OS X: added new Audio I/O preference that lets you tell Audacity
to never change any audio device settings.
* Newer libsndfile supports FLAC import and export
* Updated soundtouch to current version which is faster and better quality
* Modified configure script prefers system libraries to local copies to
reduce compilation times and memory usage.
* Minor updates to help files.
* New or updated translations: Bulgarian (bg), Galician (gl),
Traditional Chinese (zh_TW), Simplified Chinese (zh), Slovenian (sl),
Swedish (sv), Bangladeshi (bn), Slovakian (sk), Romanian (ro),
Lithuanian (lt), Welsh (cy), and Turkish (tr).
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.
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.
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.
