either because they themselves are not ready or because a
dependency isn't. This is annotated by
PYTHON_VERSIONS_INCOMPATIBLE= 33 # not yet ported as of x.y.z
or
PYTHON_VERSIONS_INCOMPATIBLE= 33 # py-foo, py-bar
respectively, please use the same style for other packages,
and check during updates.
Use versioned_dependencies.mk where applicable.
Use REPLACE_PYTHON instead of handcoded alternatives, where applicable.
Reorder Makefile sections into standard order, where applicable.
Remove PYTHON_VERSIONS_INCLUDE_3X lines since that will be default
with the next commit.
Whitespace cleanups and other nits corrected, where necessary.
to address issues with NetBSD-6(and earlier)'s fontconfig not being
new enough for pango.
While doing that, also bump freetype2 dependency to current pkgsrc
version.
Suggested by tron in PR 47882
File too long (should be no more than 24 lines).
Line too long (should be no more than 80 characters).
Trailing empty lines.
Trailing white-space.
Trucated the long files as best as possible while preserving the most info
contained in them.
The problem with this package is that the configure step is insufficient
at determining if the math long double functions are supported. It tests
for a couple of functions and assumes that if those test pass, then all
"L" functions are supported.
When DragonFly recently upgraded its math library by adding support for a
number of long double functions, this package started failing. Support for
expl, logl, log10l, sinhl, tanhl, acoshl, asinhl, atanhl, and coshl are
still missing on *all* BSDs.
The fix for the package is to override the configure script by falsely
stating that long double is not supported. Only kcalc uses long double so
this misconfiguration only has the effect to cause kcalc to use the
standard double math functions. FreeBSD almost definitely needs the same
Makefile fix.
No revbump is needed because pre-libm improved DragonFly releases are
configured the same way.
assumes "tar rvf ..." works when archive doesn't already exist.
assumes "tar tvf ..." doesn't produce an error on a zero length file.
assumes "tar --delete" works.
so depend on gtar always and fix setting of TarExe so that it uses it.
Bump PKGREVISION.
