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.
Summary of changes:
- removal of USE_GTEXINFO
- addition of mk/texinfo.mk
- inclusion of this file in package Makefiles requiring it
- `install-info' substituted by `${INSTALL_INFO}' in PLISTs
- tuning of mk/bsd.pkg.mk:
removal of USE_GTEXINFO
INSTALL_INFO added to PLIST_SUBST
`${INSTALL_INFO}' replace `install-info' in target rules
print-PLIST target now generate `${INSTALL_INFO}' instead of `install-info'
- a couple of new patch files added for a handful of packages
- setting of the TEXINFO_OVERRIDE "switch" in packages Makefiles requiring it
- devel/cssc marked requiring texinfo 4.0
- a couple of packages Makefiles were tuned with respect of INFO_FILES and
makeinfo command usage
See -newly added by this commit- section 10.24 of Packages.txt for
further information.
set FOO_CONFIG=${BUILDLINK_CONFIG_WRAPPER.foo} in both CONFIGURE_ENV and
MAKE_ENV. We remove the check for GNU_CONFIGURE because if a package
Makefile includes the buildlink.mk file, then it most likely wants to use
the config script wrappers as well. Change suggested by Hubert Feyrer
(hubertf) and Tomasz Luchowski (zuntum).
BUILDLINK_PREFIX.<pkgname>. This allows buildlink to find X11BASE packages
regardless of whether they were installed before or after xpkgwedge was
installed. Idea by Alistair Crooks <agc@pkgsrc.org>.
so remove it from package Makefiles. Also move the inclusion of the
buildlink.mk files to the end of the Makefile to just before bsd.pkg.mk
to ensure that any Makefile settings occur before the buildlink.mk files.
FOO_REQD=1.0 being converted to foo>=1.0, one can now directly specify
the dependency pattern as FOO_DEPENDS=foo>=1.0. This allows things like
JPEG_DEPENDS=jpeg-6b, or fancier expressions like for postgresql-lib.
Change existing FOO_REQD definitions in Makefiles to FOO_DEPENDS.