Up to [cvs.NetBSD.org] / pkgsrc / print / ghostscript-agpl
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
*: revbump for icu downgrade
*: recursive bump for icu 76.1 shlib bump
print/ghostscript-agpl: don't run ./configure with unknown options
ghostscript-agpl: update to 10.04.0 Version 10.04.0 (2024-09-18) Highlights in this release include: • This release addresses CVEs: CVE-2024-46951, CVE-2024-46952, CVE-2024-46953, CVE-2024-46954, CVE-2024-46955, CVE-2024-46956 • IMPORTANT: In this release (10.04.0) we have be added protection for device selection from PostScript input. This will mean that, by default, only the device specified on the command line will be permitted. Similar to the file permissions, there will be a "--permit-devices=" allowing a comma separation list of allowed devices. This will also take a single wildcard "*" allowing any device. Any application which relies on allowing PostScript to change devices during a job will have to be aware, and take action to deal with this change. The exception is "nulldevice", switching to that requires no special action. • Our efforts in code hygiene and maintainability continue. • The usual round of bug fixes, compatibility changes, and incremental improvements.
ghostscript-agpl: fix build w/ GCC 14
revbump after icu and protobuf updates
ghostscript-agpl: update to 10.03.1. Version 10.03.1 (2024-05-02) Highlights in this release include: • Fixes for CVE-2024-33869, CVE-2023-52722, CVE-2024-33870, CVE-2024-33871 and CVE-2024-29510 • IMPORTANT: For the 10.04.0 release (fall/autumn 2024) we will be adding protection for device selection from PostScript input. This will mean that, by default, only the device specified on the command line will be permitted. Similar to the file permissions, there will be a "--permit-devices=" allowing a comma separation list of allowed devices. This will also take a single wildcard "*" allowing any device. Any application which relies on allowing PostScript to change devices during a job will have to be aware, and take action to deal with this change. The exception is "nulldevice", switching to that requires no special action. • A vulnerability was identified in the way Ghostscript/GhostPDL called tesseract for the OCR devices, which could allow arbitrary code execution. As as result, we strongly urge anyone including the OCR devices in their build to update as soon as possible. • As of this release (10.03.1) pdfwrite creates PDF files with XRef streams and ObjStm streams. This can result in considerably smaller PDF output files. See Vector Devices for more details. • Ghostscript/pdfwrite now supports passing through PDF "Optional Content". • Our efforts in code hygiene and maintainability continue. • The usual round of bug fixes, compatibility changes, and incremental improvements. • (9.53.0) We have added the capability to build with the Tesseract OCR engine. In such a build, new devices are available (pdfocr8/pdfocr24/ pdfocr32) which render the output file to an image, OCR that image, and output the image "wrapped" up as a PDF file, with the OCR generated text information included as "invisible" text (in PDF terms, text rendering mode 3). Mainly due to time constraints, we only support including Tesseract from source included in our release packages, and not linking to Tesseract/ Leptonica shared libraries. Whether we add this capability will be largely dependent on community demand for the feature. See Enabling OCR for more details.
*: recursive bump for gnutls p11-kit option (existing installations need the bl3.mk included, but it's now only optionally included)
ghostscript-agpl: update to 10.03.0. Version 10.03.0 (2024-03-06) Highlights in this release include: • A vulnerability was identified in the way Ghostscript/GhostPDL called tesseract for the OCR devices, which could allow arbitrary code execution. As as result, we strongly urge anyone including the OCR devices in their build to update as soon as possible. • As of this release (10.03.0) pdfwrite creates PDF files with XRef streams and ObjStm streams. This can result in considerably smaller PDF output files. See Vector Devices for more details. • Ghostscript/pdfwrite now supports passing through PDF "Optional Content". • Our efforts in code hygiene and maintainability continue. • The usual round of bug fixes, compatibility changes, and incremental improvements. Incompatible changes • (10.03.0) Almost all the "internal" PostScript procedures defined during the interpreter startup are now "executeonly", further reducing the attack surface of the interpreter. The nature of these procedures means there should be no impact for legitimate usage, but it is possible it will impact uses which abuse the previous accessibility (even for legitimate reasons). Such cases may now require "DELAYBIND", See DELAYBIND • (10.03.0) The "makeimagedevice" non-standard operator has been removed. It allowed low level access to the graphics library in a way that was, essentially impossible to secure. • (10.03.0) The "putdeviceprops", "getdeviceprops", "finddevice", "copydevice", "findprotodevice" non-standard operators have all been removed. They provided functionality that is either accessible through standard operators, or should not be used by user PostScript. • (10.03.0) The process of "tidying" the PostScript namespace should have removed only non-standard and undocumented operators. Nevertheless, it is possible that any integrations or utilities that rely on those non-standard and undocumented operators may stop working or may change behaviour. If you encounter such a case, please contact us (Discord, #ghostscript IRC channel, or the gs-devel mailing list would be best), and we'll work with you to either find an alternative solution or return the previous functionality, if there is genuinely no other option.
ghostscript-agpl: fix CONFLICTS pattern for gambc Fixes PR 57697.
*: revebump for new brotli option for freetype2 Addresses PR 57693
*: recursive bump for icu 74.1
ghostscript-agpl: updated to 10.02.1 Ghostscript/GhostPDL 10.02.1 Patch release to address some security bugs
*: bump for openssl 3
recursive revbump for tiff update
Pullup ticket #6776 - requested by bsiegert print/ghostscript-agpl: security update Revisions pulled up: - print/ghostscript-agpl/Makefile 1.77 - print/ghostscript-agpl/Makefile.common 1.30 - print/ghostscript-agpl/distinfo 1.45 ------------------------------------------------------------------- Module Name: pkgsrc Committed By: adam Date: Mon Jun 26 11:27:25 UTC 2023 Modified Files: pkgsrc/print/ghostscript-agpl: Makefile Makefile.common distinfo Log Message: ghostscript-agpl: updated to 10.01.2 Version 10.01.2 (2023-06-21) Highlights in this release include: We've continued to improve the performance of the PDF interpreter written in C and improve it's behaviour in edge and out-of-specification cases. Our efforts in code hygiene and maintainability continue. The usual round of bug fixes, compatibility changes, and incremental improvements. (9.53.0) We have added the capability to build with the Tesseract OCR engine. In such a build, new devices are available (pdfocr8/pdfocr24/pdfocr32) which render the output file to an image, OCR that image, and output the image "wrapped" up as a PDF file, with the OCR generated text information included as "invisible" text (in PDF terms, text rendering mode 3). To generate a diff of this commit: cvs rdiff -u -r1.76 -r1.77 pkgsrc/print/ghostscript-agpl/Makefile cvs rdiff -u -r1.29 -r1.30 pkgsrc/print/ghostscript-agpl/Makefile.common cvs rdiff -u -r1.44 -r1.45 pkgsrc/print/ghostscript-agpl/distinfo
ghostscript-agpl: updated to 10.01.2 Version 10.01.2 (2023-06-21) Highlights in this release include: We've continued to improve the performance of the PDF interpreter written in C and improve it's behaviour in edge and out-of-specification cases. Our efforts in code hygiene and maintainability continue. The usual round of bug fixes, compatibility changes, and incremental improvements. (9.53.0) We have added the capability to build with the Tesseract OCR engine. In such a build, new devices are available (pdfocr8/pdfocr24/pdfocr32) which render the output file to an image, OCR that image, and output the image "wrapped" up as a PDF file, with the OCR generated text information included as "invisible" text (in PDF terms, text rendering mode 3).
ghostscript-agpl: conflicts with lang/gambc
ghostscript-agpl: update to 10.01.0. Version 10.01.0 (2023-03-22) Highlights in this release include: • We've continued to improve the performance of the PDF interpreter written in C and improve it's behaviour in edge and out-of-specification cases. • Our efforts in code hygiene and maintainability continue. • The usual round of bug fixes, compatibility changes, and incremental improvements.
revbump after textproc/icu update
*: recursive PKGREVISION bump for libpaper shlib major bump
*: Recursive revbup from graphics/freetype2
ghostscript-agpl: updated to 10.0.0 Version 10.00.0 (2022-08-18) Highlights in this release include: The big change in this release is that the old PDF interpreter (written in PostScript) is now fully deprecated. We will not be making any further changes to it. For this release, the -dNEWPDF=false option remains for "emergency" use, but the option to fall back to the old intepreter will also be removed in the next full release (10.01.0) in spring 2023. So we once again encourage all users to test the new interpreter in their use cases, and report any problems. The new PDF interpreter written in C has had several performance improvements. It was already quicker for the majority of cases than the PostScript implementation, but we found further improvements for common cases, and also several speed improvements in edge cases. Our efforts in code hygiene and maintainability continue. The usual round of bug fixes, compatibility changes, and incremental improvements. (9.53.0) We have added the capability to build with the Tesseract OCR engine. In such a build, new devices are available (pdfocr8/pdfocr24/pdfocr32) which render the output file to an image, OCR that image, and output the image "wrapped" up as a PDF file, with the OCR generated text information included as "invisible" text (in PDF terms, text rendering mode 3). Mainly due to time constraints, we only support including Tesseract from source included in our release packages, and not linking to Tesseract/Leptonica shared libraries. Whether we add this capability will be largely dependent on community demand for the feature. See Enabling OCR for more details.
*: recursive bump for tiff shlib major bump
*: bump PKGREVISION for libunistring shlib major bump
Bump everything affected by the jpeg.buildlink3.mk fix.
*: recursive bump for perl 5.36
ghostscript-agpl: updated to 9.56.1 9.56.1 New PDF Interpreter is now enabled by default: See Changes Coming to the PDF Interpreter libgs is now threadsafe The PSD output devices now write ICC profiles to their output files for improved color fidelity. Ghostscript/GhostPDL can now output Apple Raster and URF format image files: via the "appleraster" or "urf" output devices (using the cups implementation of those formats).
ghostscript-agpl: Fix build issue discussed on pkgsrc-users@ https://mail-index.netbsd.org/pkgsrc-users/2019/06/13/msg028790.html This fix has kindly been provided upstream to try solving the building errors (https://bugs.ghostscript.com/show_bug.cgi?id=704844).
revbump for icu and libffi
ghostscript-*: Support GCC >= 10.
ghostscript-agpl: updated to 9.54.0 The 9.54.0 release is a maintenance release, and also adds new functionality. Highlights in this release include: Overprint simulation is now available to all output devices, allowing quality previewing/proofing of PostScript and PDF jobs that rely on overprint. See the -dOverprint option documentation in: Overprint The "docxwrite" device adds the ability to output to Microsoft Word "docx" format. See: docxwrite The pdfwrite device is now capable of using the Tesseract OCR engine when it is built into Ghostscript to improve searchability and copy and paste functionality when the input lacks the metadata for that purpose. See: UseOCR Ghostscript/GhostPDL now includes a "map text to black" function, where text drawn by an input job (except when drawn using a Type 3 font) can be forced to draw in solid black. See: BlackText Ghostscript/GhostPDL now supports simple N-up imposition "internally". See: NupControl Our efforts in code hygiene and maintainability continue. The usual round of bug fixes, compatibility changes, and incremental improvements. (9.53.0) We have added the capability to build with the Tesseract OCR engine. In such a build, new devices are available (pdfocr8/pdfocr24/pdfocr32) which render the output file to an image, OCR that image, and output the image "wrapped" up as a PDF file, with the OCR generated text information included as "invisible" text (in PDF terms, text rendering mode 3). Mainly due to time constraints, we only support including Tesseract from source included in our release packages, and not linking to Tesseract/Leptonica shared libraries. Whether we add this capability will be largely dependent on community demand for the feature.
*: recursive bump for perl 5.34
revbump for boost-libs
Pullup ticket #6354 - requested by maya print/ghostscript-agpl: dependecy update triggered build fix Revisions pulled up: - print/ghostscript-agpl/Makefile patch - print/ghostscript-agpl/distinfo patch - print/ghostscript-agpl/patches/patch-base_fapi__ft.c 1.1 Make the package build with FreeType 2.10.3.
ghostscript-agpl: Update to 9.53.0 pkgsrc changes (for fonts/ghostscript-cidfonts-ryumin): - Add SUBST_NOOP_OK.ttf_path, at least for the default `cidfmap-adobe' that's a noop Changes: 9.53.0 ====== Highlights in this release include: - The 9.53.0 release is primarily maintenance. - The most obvious change is the (re-)introduction of the patch level to the version number, this helps facilitate a revised policy on handling security related issues. - Our efforts in code hygiene and maintainability continue. - We have added the capability to build with the Tesseract OCR engine. In such a build, new devices are available (pdfocr8/pdfocr24/pdfocr32) which render the output file to an image, OCR that image, and output the image "wrapped" up as a PDF file, with the OCR generated text information included as "invisible" text (in PDF terms, text rendering mode 3). Due to some patches to the Tesseract sources that are required (integrated upstream, but awaiting release), time constraints, and the experimental nature of the feature, we only support including Tesseract from source, not linking to Tesseract shared libraries. Whether we add this capability will be largely dependant on community demand for the feature. - We have added Python bindings for the gsapi interface, can be found in demos/python. These are experimental, and we welcome feedback from interested developers. - For those integrating Ghostscript/GhostPDL via the gsapi interface, we have added new capabilities to that, specifically in terms of setting and interrogating device parameters. These, along with the existing interface calls, are documented in: Ghostscript Interpreter API - IMPORTANT: In consultation with a representative of (OpenPrinting) it is our intention to deprecate and, in the not distant future, remove the OpenPrinting Vector/Raster Printer Drivers (that is, the opvp and oprp devices). If you rely on either of these devices, please get in touch with us, so we can discuss your use case, and revise our plans accordingly. - IMPORTANT: We have forked LittleCMS2 into LittleCMS2mt (the "mt" indicating "multi-thread"). LCMS2 is not thread safe and cannot be made thread safe without breaking the ABI. Our fork will be thread safe and include performance enhancements (these changes have all be been offered and rejected upstream). We will maintain compatibility between Ghostscript and LCMS2 for a time, but not in perpetuity. If there is sufficient interest, our fork will be available as its own package separately from Ghostscript (and MuPDF). - The usual round of bug fixes, compatibility changes, and incremental improvements.
*: bump PKGREVISION for perl-5.32.
*: revbump after fontconfig bl3 changes (libuuid removal)
Enable cups option by default and pull in libcups instead of cups-base. Bump pkg revision.
revbump after updating security/nettle
ghostscript-agpl: updated to 9.52 Version 9.52: Highlights in this release include: The 9.52 release replaces the 9.51 release after a problem was reported with 9.51 which warranted the quick turnaround. Thus, like 9.51, 9.52 is primarily a maintenance release, consolidating the changes we introduced in 9.50. We have continued our work on code hygiene for this release, with a focus on the static analysis tool Coverity (from Synopsys, Inc) and we have now adopted a policy of maintaining zero Coverity issues in the Ghostscript/GhostPDL source base. IMPORTANT: In consultation with a representative of (OpenPrinting) it is our intention to deprecate and, in the not distant future, remove the OpenPrinting Vector/Raster Printer Drivers (that is, the opvp and oprp devices). If you rely on either of these devices, please get in touch with us, so we can discuss your use case, and revise our plans accordingly. IMPORTANT: We have forked LittleCMS2 into LittleCMS2mt (the "mt" indicating "multi-thread"). LCMS2 is not thread-safe, and cannot be made thread-safe without breaking the ABI. Our fork will be thread-safe and include performance enhancements (these changes have all be been offered and rejected upstream). We will maintain compatibility between Ghostscript and LCMS2 for a time, but not in perpetuity. If there is sufficient interest, our fork will be available as its own package separately from Ghostscript (and MuPDF). The usual round of bug fixes, compatibility changes, and incremental improvements.
librsvg: update bl3.mk to remove libcroco in rust case recursive bump for the dependency change
*: recursive bump for libffi
ghostscript-agpl: fix dvipdf
Pullup ticket #6109 - requested by sevan print/ghostscript-agpl: security fix Revisions pulled up: - print/ghostscript-agpl/Makefile 1.49 - print/ghostscript-agpl/distinfo 1.27 - print/ghostscript-agpl/patches/patch-Resource_Init_gs_ttf.ps 1.1 --- Module Name: pkgsrc Committed By: sevan Date: Fri Jan 3 23:56:09 UTC 2020 Modified Files: pkgsrc/print/ghostscript-agpl: Makefile distinfo Added Files: pkgsrc/print/ghostscript-agpl/patches: patch-Resource_Init_gs_ttf.ps Log Message: Patch CVE-2019-14869
(print/ghostscript-agpl) Delete garbage from DESTDIR
Patch CVE-2019-14869
ghostscript-agpl: Really use graphics/lcms2 The bundled lcms2mt was still accidentally picked up making packages linked against graphics/lcms2 aborting (e.g. ImageMagick) when handling format that used ghostscript-agpl. PKGREVISION++
ghostscript-agpl: Update to 9.50 Changes: Version 9.50 (2019-09-30) Highlights in this release include: * The change to version 9.50 (rather than the intended 9.28) follows recognition of the extent and importance of the file access control redesign/reimplementation outlined below. * The file access control capability (enable with -dSAFER) has been completely rewritten, with a ground-up rethink of the design. For more details, see: SAFER. It is important to note that -dSAFER now only enables the file access controls, and no longer applies restrictions to standard Postscript functionality (specifically, restrictions on setpagedevice. If your application relies on these Postscript restrictions, see OLDSAFER, and please get in touch, as we do plan to remove those Postscript restrictions unless we have reason not to. IMPORTANT: File access controls are now enabled by default. In order to run Ghostscript without these controls, see NOSAFER Important Note for Windows Users: See below under Incompatible Changes * IMPORTANT: We are in the process of forking LittleCMS. LCMS2 is not thread safe, and cannot be made thread safe without breaking the ABI. Our fork will be thread safe, and include performance enhancements (these changes have all be been offered and rejected upstream). We will maintain compatibility between Ghostscript and LCMS2 for a time, but not in perpetuity. Our fork will be available as its own package separately from Ghostscript (and MuPDF). * The usual round of bug fixes, compatibility changes, and incremental improvements. * Special thanks to Akira Kakuto, Paul Wessel, William Bader, Nelson H. F. Beebe and everyone else who put time and effort into testing this new release. For a list of open issues, or to report problems, please visit bugs.ghostscript.com. Incompatible changes * There are a couple of subtle incompatibilities between the old and new SAFER implementations. Firstly, as mentioned above, SAFER now leaves standard Postcript functionality unchanged (except for the file access limitations). Secondly, the interaction with save/restore operations, see SAFER. Important Note for Windows Users: The file/path pattern matching is case sensitive, even on Windows. This is a change in behaviour compared to the old code which, on Windows, was case insensitive. This is in recognition of changes in Windows behaviour, in that it now supports (although does not enforce) case sensitivity. * The following is not strictly speaking new to 9.50, as not much has changed since 9.27 in this area, but for those who don't upgrade with every release: The process of "tidying" the Postscript name space should have removed only non-standard and undocumented operators. Nevertheless, it is possible that any integrations or utilities that rely on those non-standard and undocumented operators may stop working, or may change behaviour. If you encounter such a case, please contact us (either the #ghostscript IRC channel, or the gs-devel mailing list would be best), and we'll work with you to either find an alternative solution or return the previous functionality, if there is genuinely no other option. One case we know this has occurred is GSView 5 (and earlier). GSView 5 support for PDF files relied upon internal use only features which are no longer available. GSView 5 will still work as previously for Postscript files. For PDF files, users are encouraged to look at MuPDF.
Bump PKGREVISIONs for perl 5.30.0
*: recursive bump for gdk-pixbuf2-2.38.1
*: recursive bump for nettle 3.5.1
ghostscript-agpl: cosmetic change
ghostscript-agpl: Require freetype2>=2.10.0 The latest version of ghostscript-agpl calls functions that were introduced in freetype2 version 2.10.0, and the build fails when building against an earlier version.
ghostscript-agpl: updated to 9.27 Version 9.27: Highlights in this release include: We have extensively cleaned up the Postscript name space: removing access to internal and/or undocumented Postscript operators, procedures and data. This has benefits for security and maintainability. We have added a new "product": "gpdl". This is a rethink/redesign of the old "language_switch" product (pspcl6), and includes all the interpreters we develop based on the Ghostscript graphics library: Postscript, PDF, PCL6, PXL and XPS. This is experimental, and should be considered of beta testing quality, and thus is not built by default: it can be built by using the "experimental" target. gpdl uses a heuristic to judge the file type being passed to it. In general, it supports most of the widely used command line options for each interpreter, but compatibility is not complete (the practicalities of swapping interpreters means it is unlikely that full parity of command line options will be possible). Fontmap can now reference invidual fonts in a TrueType Collection for font subsitution. Previously, a Fontmap entry could only reference a TrueType collection and use the default (first) font. Now, the Fontmap syntax allows for specifying a specific index in a TTC. See the comments at the top of (the default) Fontmap.GS for details. IMPORTANT: We are in the process of forking LittleCMS. LCMS2 is not thread safe, and cannot be made thread safe without breaking the ABI. Our fork will be thread safe, and include performance enhancements (these changes have all be been offered and rejected upstream). We will maintain compatibility between Ghostscript and LCMS2 for a time, but not in perpetuity. Our fork will be available as its own package separately from Ghostscript (and MuPDF). The usual round of bug fixes, compatibility changes, and incremental improvements.
print/ghostscript-agpl: Add upstream bug URL about labeling Upstream calls this "GPL Ghostscript" which is at best confusing. (Thanks to rhialto@ for filing the upstream bug report.)
Recursive bump for ghostscript default change
print/ghostscript-agpl: Reduce diffs to -gpl Reorder lines in a way that should have no functional effect, but which makes Makefile closer to ../print/ghostscript-gpl/Makefile.
ghostscript-agpl: Switch to use pkgsrc openjpeg instead of bundled one Remove bundled openjpeg in WRKSRC, add a dependency to openjpeg and pass `--enable-openjpeg' in order to always link to pkgsrc one instead of the ghostscript bundled one. Bump PKGREVISION.
print/ghostscript-agpl: pkglint cleanups - Add \todo about a4 not being valid for PAPERSIZE - Add PAPERSIZE to BUILD_DEFS - Add \todo about jpeg2000 bl3 that is commented out without explanation - GC undefined and unused PLIST.cidfmap No real change intended, other than BUILD_DEFS. Ride recent PKGREVISION++.
print/ghostscript-agpl: Add default-off cups option This is basically a port of the cups option code from ../ghostscript-gpl. Since the last GPL3 gs release, some programs have migrated to the cups-filters package. Thus, they are no longer installed by cups, and the option is much simpler. I verified that the cups driver appears in "gs -h", but have not tested it. While the option defaults to off, I bumped PKGREVISION anyway.
ghostscript-agpl: updated to 9.24 Version 9.24: Highlights in this release include: Security issues have been the primary focus of this release, including solving several (well publicised) real and potential exploits. PLEASE NOTE: We strongly urge users to upgrade to this latest release to avoid these issues. As well as Ghostscript itself, jbig2dec has had a significant amount of work improving its robustness in the face of out specification files. IMPORTANT: We are in the process of forking LittleCMS. LCMS2 is not thread safe, and cannot be made thread safe without breaking the ABI. Our fork will be thread safe, and include performance enhancements (these changes have all be been offered and rejected upstream). We will maintain compatibility between Ghostscript and LCMS2 for a time, but not in perpetuity. Our fork will be available as its own package separately from Ghostscript (and MuPDF). The usual round of bug fixes, compatibility changes, and incremental improvements.
Recursive bump for perl5-5.28.0
ghostscript-agpl: Fix SunOS build with older compilers.
ghostscript-agpl: updated to 9.23 Version 9.23: Ghostscript now has a family of 'pdfimage' devices (pdfimage8, pdfimage24 and pdfimage32) which produce rendered output wrapped up as an image in a PDF. Additionally, there is a 'pclm' device which produces PCLm format output. There is now a ColorAccuracy parameter allowing the user to decide between speed or accuracy in ICC color transforms. JPEG Passthrough: devices which support it can now receive the 'raw' JPEG stream from the interpreter. The main use of this is the pdfwrite/ps2write family of devices that can now take JPEG streams from the input file(s) and write them unchanged to the output (thus avoiding additional quantization effects). PDF transparency performance improvements IMPORTANT: We are in the process of forking LittleCMS. LCMS2 is not thread safe, and cannot be made thread safe without breaking the ABI. Our fork will be thread safe, and include performance enhancements (these changes have all be been offered and rejected upstream). We will maintain compatibility between Ghostscript and LCMS2 for a time, but not in perpetuity. Our fork will be available as its own package separately from Ghostscript (and MuPDF). We have continued the focus on code hygiene in this release cleaning up security issues, ignored return values, and compiler warnings. The usual round of bug fixes, compatibility changes, and incremental improvements.
Recursive bumps for fontconfig and libzip dependency changes.
ghostscript-agpl: Add _XOPEN_SOURCE workaround.
Bump PKGREVISION on packages depending on CUPS This should be the last part of the renaming operation for print/cups to print/cups-base. Rationale: packages depending on CUPS but not relying on a functional printing setup only need to depend on print/cups-base (equivalent to the former print/cups). The new print/cups now depends on print/cups-base and on print/cups-filters, thus directly providing a functional printing setup. This bump reflects this change of dependency. As discussed on tech-pkg@
ghostscript-agpl: update to 9.22 Highlights in this release include: * Ghostscript can now consume and produce (via the pdfwrite device) PDF 2.0 compliant files. * The main focus of this release has been security and code cleanliness. Hence many AddressSanitizer, Valgrind and Coverity issues have been addressed. * The usual round of bug fixes, compatibility changes, and incremental improvements.
Follow some http -> https redirects.
Bump PKGREVISION for cups15 -> cups change.
Version 9.21 (2017-03-16) This is the fifteenth full release in the stable 9.x series. Highlights in this release include: * pdfwrite now preserves annotations from input PDFs (where possible). * The GhostXPS interpreter now provides the pdfwrite device with the data it requires to emit a ToUnicode CMap: thus allowing fully searchable PDFs to be created from XPS input (in the vast majority of cases). * Ghostscript now allows the default color space for PDF transparency blends. * The Ghostscript/GhostPDL configure script now has much better/fuller support for cross compiling. * The tiffscaled and tiffscaled4 devices can now use ETS (Even Tone Screening) * The toolbin/pdf_info.ps utility can now emit the PDF XML metadata. * Ghostscript has a new scan converter available (currently optional, but will become the default in a near future release). It can be enabled by using the command line option: '-dSCANCONVERTERTYPE=2'. This new implementation provides vastly improved performance with large and complex paths. * The usual round of bug fixes, compatibility changes, and incremental improvements.
nd include Makefile.common again.
Restore Makefile.common, still used by fonts/ghostscript-cidfonts-ryumin
Updated ghostscript-agpl to 9.20. Remove Makefile.common that is not used by anything, despite a comment to the contrary. Highlights in this release include: The usual round of bug fixes, compatibility changes, and incremental improvements. For a list of open issues, or to report problems, please visit bugs.ghostscript.com. Incompatible changes The planned device API tidy did not happen for this release, due to time pressures, but we still intend to undertake the following: We plan to somewhat tidy up the device API. We intend to remove deprecated device procs (methods/function pointers) and change the device API so every device proc takes a graphics state parameter (rather than the current scheme where only a very few procs take an imager state parameter). This should serve as notice to anyone maintaining a Ghostscript device outside the canonical source tree that you may (probably will) need to update your device(s) when these changes happen. Devices using only the non-deprecated procs should be trivial to update.
Bump PKGREVISION for perl-5.24.0 for everything mentioning perl.
Changes 9.19: * New custom PJL (near) equivalents for pdfmark and setdistillerparams. * Metadata pdfmark is now implemented. * An experimental, rudimentary raster trapping implementation implementation has been added to the Ghostscript graphics library. * The halftone threshold array generation tools (part of toolbin/halftone) have been improved with thresh_remap which allows folding the transfer function (AKA toner response curve (TRC)) into the threshold array so that highlights are improved. Further, gen_stochastic has improved support for minimum dot size and shape. * Plus the usual round of bug fixes, compatibility changes, and incremental improvements.
Use OPSYSVARS.
Add gserrors.h to the installed files (upstream Bug 696301)
Changes 9.18: A substantial revision of the build system and GhostPDL directory structure, meaning the GhostPCL and GhostXPS "products" are now built by the Ghostscript build system "proper" rather than having their own builds which called the Ghostscript build system for certain parts of the builds. Ghostscript-only users should not be affected by this change. For users of the PCL and XPS interpreters (collectively downloaded as "GhostPDL") there is a new, "flatter" directory structure and only one configure and one make invocation to build all the products. There are also some executable default name changes to bring the PCL and XPS binaries in line with the Ghostscript ones. All executables now end up in the "bin" directory (or build specific variant thereof, e.g. "debugbin"). The PCL executable, by default, is now "gpcl6" on Unix like systems and "gpcl6win??.exe" (where "??" is either "32" or "64"). The XPS executable remains "gxps" on Unix-like systems, but similarly becomes "gxpswin??.exe" on Windows. Those using scripts or other automated processes will need to take steps to cope with these changes. A new method of internally inserting devices into the device chain has been developed, named "device subclassing". This allows suitably written devices to be more easily and consistently as "filter" devices. The first fruit of this is a new implementation of the "-dFirstPage"/"-dLastPage" feature which functions a device filter in the Ghostscript graphics library, meaning it works consistently with all input languages. The "ghostpdl.inf" file, provided to simplify installing a Postscript printer configure to produce output to suit Ghostscript's "pdfwrite" device is now available as a digitally signed version: "ghostpdl.cat". Plus the usual round of bug fixes, compatibility changes, and incremental improvements.
Use memmove instead of memcpy in one place. It seems the arguments sometimes overlap, and _FORTIFY_SOURCE=2 causes it to dump core in this case. Bump PKGREVISION.
Recursive PKGREVISION bump for all packages mentioning 'perl', having a PKGNAME of p5-*, or depending such a package, for perl-5.22.0.
Changes 9.16: * "LockColorants" command line option for tiffsep and psdcmyk devices. Specifying -dLockColorants will restrict those devices to only the colorants list on the command line (thus: -c "<< /SeparationColorNames [ /Cyan /Magenta /Yellow /Black /Violet /Orange] /SeparationOrder [ /Cyan /Magenta /Yellow /Black /Violet /Orange]>> setpagedevice"), rather than allowing the devices to add new colorants as encountered in the input. This is, obviously, preferable for real printers, where only a certain of inks will be available. * Improved high level devices handling of Forms. Whilst High level devices (eg pdfwrite) already checked Forms to see if they are duplicates, and if so use the initial definition. However, this does not improve performance, since the Form PaintProc still needs to be executed for each instance of the Form, and the matching algorithm could, in very odd circumstances, be defeated. The new implementation benefits both causes, meaning the second and subsequent invocation of the form need not re-run the PaintProc, and removes the heurisic aspect of the reuse detection. * New URW+ fonts in which the families NimbusMono, NimbusRoman and NimbusSans have been augmented with production quality Greek and Cyrillic glyphs. These correspond to our substitutes for the PDF base 14 fonts. * Plus the usual round of bug fixes, compatibility changes, and incremental improvements.
Changes 9.15: Ghostscript now supports the PDF security handler revision 6. The pdfwrite and ps2write (and related) devices can now be forced to "flatten" glyphs into "basic" marking operations (rather than writing fonts to the output), by giving the -dNoOutputFonts command line option (defaults to "false") PostScript programs can now use get_params or get_param to determine if a page contains color markings by reading the pageneutralcolor state from the device (so whether the page is "color" or "mono"). Note that this is only accurate when in clist mode, so -dMaxBitmap=0 and -dGrayDetection=true should both be used. The pdfwrite device now supports Link annotations with GoTo and GoToR actions The pdfwrite device now supports BMC/BDC/EMC pdfmarks Regarding the new color management for the pdfwrite device introduced in the previous release, the proscription on using the new color management when producing PDF/A-1 compliant files is now lifted. To reiterate, also, with the new color management implementation, using the UseCIEColor option is strongly discouraged. For further information on the new pdfwrite color management, see: Color Conversion and Management Plus the usual round of bug fixes, compatibility changes, and incremental improvement
Bump PKGREVISION for cups -> cups15 change.
Bump for perl-5.20.0. Do it for all packages that * mention perl, or * have a directory name starting with p5-*, or * depend on a package starting with p5- like last time, for 5.18, where this didn't lead to complaints. Let me know if you have any this time.
Changes 9.14: pdfwrite now uses the same color management engine as Ghostscript rendering devices (by default LCMS2). This provides much better control over color conversion and color management generally, but will result in some small color differences when compared to the old system. It is no longer necessary to specify UseCIEColor (and we very much encourage you not to do this) or the ProcessColorModel if you want to convert a PDF file to a specific color space, simply set the ColorConversionStrategy appropriately. We do not expect any major problems to arise with this new code, but for the duration of this release a new switch -dPDFUseOldCMS is available which will restore the old color management. See: Color Conversion and Management Please note that due to constraints of the PDF/A-1 specification, the new color management does not yet apply when producing PDF/A files. A new device 'eps2write' has been added which allows for the creation of EPS files using the ps2write device instead of the old (deprecated and removed) pswrite device. This produces considerably better quality EPS files than the old epswrite device which is now also deprecated and will be removed in a future release. ps2write now has a feature to allow customisation of the output for specific devices. Please see PSDocOptions and PSPageOptions described in ps2ps2.htm Additional Distiller Params Ghostscript now reduces memory usage when processing PDF files that use transparency and output is to display devices such as Windows display or x11 (i.e. devices that are strictly full framebuffer devices), and to high level vector devices that cannot reproduce the PDF transparency model, such as the ps2write device or pdfwrite when 'flattening' to PDF 1.3 or earlier (-dCompatibilityLevel=1.3). This uses banding (clist) files to render the transparent areas in bands to reduce memory use, and unlike the existing page level banding, this is hidden from the target device. Ghostscript can now collect information for pages in temp files (in Ghostscript's clist format), then render and output pages for the job in arbitrary order, including normal, reverse, odd, even, or any order or subset of the pages. This is controlled with the --saved-page=___ option. (Note that this only applies to rendering devices, and not high level devices such as pdfwrite and ps2write.) See: Deferred Page Rendering The Ghostscript device architecture has been extended so that, when rendering bands into multiple threads, it is now possible to perform post-processing in multiple threads, such as downscale, post-render halftoning, or compression. Previously, post processing was only possible in the single main thread. This can improve performance significantly. Ghostscript has a new "pwgraster" output device for PWG Raster output The CUPS device now has improved support for PPD-less printing Plus the usual round of bug fixes, compatibility changes, and incremental improvements.
Recursive PKGREVISION bump for OpenSSL API version bump.
Drop nonfunctional cups option, following upstream. Upstream removed cups support and created a new "cups-filter" package instead. Since then, building ghostscript-agpl with the cups option has failed. This commit removes the cups option, and should result in zero changes to packages built without the cups option, and hence does not PKGREVISION++. There is still some cups configure code, which is forced off (as it was without the option). It's not clear if this configure code should also be removed (by upstream), or if it's a separate bit of cups functionality. Addressing this issue and adding a cups-filter package is left for future work, after the branch.
Changes 9.09: * Background printing (BGPrint) is a new feature allowing an accumulated page clist to be rendered by one or more rendering threads whilst the interpreter (in the "main" thread) continues to accumulate the subsequent page's clist. For certain classes of file this can result in a useful performance increase. * GrayDetection allows suitably written devices to detect "color" input in near neutral tones (i.e. near monochrome) and to convert "on-the-fly" to pure grayscale, whilst retaining the ability to print full color on demand. This is primarily aimed at workflows where saving ink (especially color inks) is required. * LittleCMS2 and libpng have both been updated to the latest versions. * Support has been added to build the Ghostscript DLL for WinRT for x86, x64 and ARM (Requires MS Visual Studio 2012 Pro). * Processing of Windows command line arguments into UTF8 (as presaged a few releases ago) has been enhanced and enabled by default. * The URW Postscript font set has been updated to the latest version, fixing many compatibility problems with the Adobe fonts. * Plus the usual round of bug fixes, compatibility changes, and incremental improvements.
Try to fix the fallout caused by the fix for PR pkg/47882. Part 3: Recursively bump package revisions again after the "freetype2" and "fontconfig" handling was fixed.
Bump freetype2 and fontconfig dependencies to current pkgsrc versions, 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
Bump all packages for perl-5.18, that a) refer 'perl' in their Makefile, or b) have a directory name of p5-*, or c) have any dependency on any p5-* package Like last time, where this caused no complaints.
Fix typo in CONFIGURE_ARGS, from Richard Palo.
Add ghostscript-agpl package, the same as the current print/ghostscript.