libmikmod-3.1.12 was released on 15/12/2007
This is bugfix release by denis111(keygenmusic).
BUGFIXES
- libmikmod no more hangs on loading XM modules with incorrect number of
instrumens.
- modules with more then 255 orders are now supported
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.
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
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).
makeinfo if no native makeinfo executable exists. Honor TEXINFO_REQD
when determining whether the native makeinfo can be used.
* Remove USE_MAKEINFO and replace it with USE_TOOLS+=makeinfo.
* Get rid of all the "split" argument deduction for makeinfo since
the PLIST module already handles varying numbers of split info files
correctly.
NOTE: Platforms that have "makeinfo" in the base system should check
that the makeinfo entries of pkgsrc/mk/tools.${OPSYS}.mk are
correct.
Also:
On NetBSD, libmikmod dynamically loads esound, so there is
no library dependency -- do not include esound bl3.mk in those
cases.
XXX: please check other OPSYS if they do the same, and add cases
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".
Summary of changes between libmikmod 3.1.11 and libmikmod 3.1.11-a
========================================================================
libmikmod-3.1.11-a was released on 05/03/2004
Most of my work and attention goes on the 3.2.x series, but I still receive
occasional bug reports and patchs for the 3.1.11 version. There are not enough
changes to make a full release, but many people may find this patch useful.
BUGFIXES
- libmikmod playback now works correcly on amd64 (type size problem)
- fixed warning issued by automake >= 1.8
- config.sub and config.guess updated
Summary of changes between libmikmod 3.1.10 and libmikmod 3.1.11 (Thiers):
==========================================================================
libmikmod 3.1.11 was released on 01/21/2004.
This is a small maintenance release. I know there are not many changes,
but since it has been a very long time since the last one, and meanwhile
libmikmod changed maintaner, I think it is justified.
THANKS
- Ingo Saitz, the maintainer of the mikmod packages for debian, for
bugfixes.
- Frank Loemker, for the lcc-win32 stuff and fixes for the direct sound
driver.
BUGFIXES
- Playback problems in MODs of length >128. This fixes the file beatwave.mod. Thanks
to Emmanuel Coirier for pointing this out.
- Applied debian patches:
- Fix for broken volume fadeouts of IT instruments
- Fixed configure test for pthread
- devfs support for Linux OSS
- Makefile for lcc-win32. To compile libmikmod with lcc-win32 a rather new
version is needed. I currently use version 3.7 compiled on Jan 20 2002.
A version half a year old did not work.
To compile
- check that you have the lcc bin directory in the PATH
(and no other compiler bin dirs),
- change to libmikmod-3.1.11/win32,
- check Makefile.lcc for any needed changes, and
- use make -f Makefile.lcc.
- Different fixes for the direct sound driver:
- Pausing did only work for half of the buffer.
- Restarting the player did not work as the output thread was removed
in DS_PlayStop().
- Removed busy waiting for end of thread.
- Sound output is started immediately on the first call to DS_Update()
to be consistent with other non threaded drivers.
- Different small clean ups.
- In MikMod_Reset() the raw output driver driver did not use the
filename set via the cmdline.
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.
