Next | Query returned 120 messages, browsing 51 to 60 | Previous

History of commit frequency

CVS Commit History:


   2019-12-13 12:25:01 by Leonardo Taccari | Files touched by this commit (1)
Log message:
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++
   2019-12-10 11:44:09 by Leonardo Taccari | Files touched by this commit (3)
Log message:
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.
   2019-08-11 15:25:21 by Thomas Klausner | Files touched by this commit (3557)
Log message:
Bump PKGREVISIONs for perl 5.30.0
   2019-07-22 00:26:08 by Thomas Klausner | Files touched by this commit (1256)
Log message:
*: recursive bump for gdk-pixbuf2-2.38.1
   2019-07-21 00:46:59 by Thomas Klausner | Files touched by this commit (595)
Log message:
*: recursive bump for nettle 3.5.1
   2019-05-06 16:53:44 by Takahiro Kambe | Files touched by this commit (1)
Log message:
print/ghostscript-agpl: fix PLIST

Fix PLIST when disable-compile-inits PKG_OPTIONS is enabled.
   2019-04-26 17:28:18 by Gavan Fantom | Files touched by this commit (1)
Log message:
ghostscript-agpl: cosmetic change
   2019-04-26 17:19:18 by Gavan Fantom | Files touched by this commit (1)
Log message:
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.
   2019-04-17 10:28:44 by Adam Ciarcinski | Files touched by this commit (5) | Package updated
Log message:
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.
   2019-03-24 01:36:28 by Greg Troxel | Files touched by this commit (1)
Log message:
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.)

Next | Query returned 120 messages, browsing 51 to 60 | Previous