|
From: | Leo Famulari |
Subject: | Re: Switching to Artifex Ghostscript |
Date: | Mon, 29 May 2017 18:14:57 -0400 |
User-agent: | Mutt/1.8.2 (2017-04-18) |
On Mon, May 29, 2017 at 08:38:58PM +0200, Ricardo Wurmus wrote: > Leo Famulari <address@hidden> writes: > > > Here are patches that allow you build groff, cairo, and cups with the > > Artifex Ghostscript. > > Woo! Actually tested and it works! > > + (patches (search-patches "artifex-ghostscript-runpath.patch" > > + ;; TODO: > > + ;;"ghostscript-CVE-2017-8291.patch" > > + )) > > What’s up with this? Is the latest release of Artifex Ghostscript > vulnerable? I added this patch in v2 of the patch series (attached). > > + (replace 'build > > + (lambda _ > > + ;; Build 'libgs.so', but don't build the statically-linked > > 'gs' > > + ;; binary (saves 22 MiB). > > + (zero? (system* "make" "so" "-j" > > + (number->string > > (parallel-job-count)))))) > > Couldn’t we just add “#:make-flags '("so")” and avoid replacing the > build phase? It seems to work. How should we make this transition? Should we add Artifex Ghostscript and transition packages over to it, wait for the next core-updates, or something else?
0001-gnu-Add-Artifex-Ghostscript.patch
Description: Text document
0002-gnu-ijs-Use-modify-phases-syntax.patch
Description: Text document
0003-gnu-ijs-Update-to-9.21.0-and-switch-to-Artifex-Ghost.patch
Description: Text document
signature.asc
Description: PGP signature
[Prev in Thread] | Current Thread | [Next in Thread] |