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).
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.
Package changes:
The include files moved from $PREFIX/include/lcms to
$PREFIX/include. Support added to buildlink*.mk to provide
compatibility symlinks include/lcms/*.h in BUILDLINK_DIR.
No list of changes since the previously packaged version (1.06), I do not
even know if there was any versions in between... Anyway changes
in version 1.12 are (from the homepage):
- Brightness/Contrast/Hue/Saturation/WhitePoint modification across abstract
profile
- License changed to MIT
- pseq tag handling: cmsReadProfileSequenceDescription and cmsSEQ,
cmsPSEQDESC structures
- CRD generation now supports black point compensation, see
cmsGetPostScriptCRDEx
- cmsTakeManufacturer and cmsTakeModel for uncooked info on these tags
- Writing 8 bit profiles is now supported
- Named color profiles support. This turns lcms from a "wide subset" into
a "full implementation" of ICC 3.4, with some ICC 4.0 support.
- PostScript CSA, CRD generation
- Ink-Limiting capabilities for CMYK
- Devicelink profile generation.
- Gray scale virtual profiles
- Linearization virtual device link profiles
- New ICCLINK and ICC2PS utilities
- SWIG wrapper. This enables lcms from Python.
- Floating-point formats are now accepted as well.
- More ICC 4.0 compatibility. Some 4.0 profiles are now are fully understood
(still experimental)
- Profiles can now be saved to memory (thanks to Steven Greaves for providing
the code)
- Char Target data are now handled. Some profiles does store the data
profiler has used. This is all information needed to rebuild the profile
from scratch.
- New low-resolution flag cmsFLAGS_LOWRESPRECALC to save memory.
- User-defined encodings are now supported.
- cmsChangeBuffersFormat() to change the encoding of buffers on runtime
allows reuse of existing transforms.
- Gamma estimation routines cmsEstimateGamma() and cmsEstimateGammaEx()
- multilocalized unicode is now supported. Language and codepage is
selected via cmsSetLanguage() (ICC 4.0 only)
- LUT handling has been enhanced with enumerators. (SAMPLER_INSPECT)
- Improved TIFFICC, JPEGICC and ICCTRANS utilities.
- cmsOpenProfileFromMem() no longer creates temporary files.
- Transforms does accept now a maximum of 8 channels on input and 16 on
output. (last version did accept 6 on input)
- 8 <-> 16 bits per sample are now always computed accurately.
- Some minor bugs fixed
the normal case when BUILDLINK_DEPENDS.<pkg> isn't specified, it receives
a value only once due to the multiple inclusion protection in the
bulldlink3.mk files. In the case where a package includes several
buildlink3.mk files that each want a slightly different version of another
dependency, having BUILDLINK_DEPENDS.<pkg> be a list allows for the
strictest <pkg> dependency to be matched.
