unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Switching to Artifex Ghostscript
Date: Tue, 23 May 2017 22:42:45 +0200	[thread overview]
Message-ID: <87inkr8fui.fsf@gnu.org> (raw)
In-Reply-To: <87vaougxzy.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 21 May 2017 15:06:41 +0200")

Ricardo Wurmus <rekado@elephly.net> skribis:

> Marius Bakke <mbakke@fastmail.com> writes:
>
>> Leo Famulari <leo@famulari.name> writes:
>>
>>> The subject of the two Ghostscripts came up last October, but we didn't
>>> really discuss it:
>>>
>>> https://lists.gnu.org/archive/html/guix-devel/2016-10/msg00598.html
>>>
>>> The canonical Ghostscript is developed by Artifex Software Inc:
>>>
>>> https://ghostscript.com/
>>>
>>> We package GNU Ghostscript, which is a fork of Artifex's Ghostscript:
>>>
>>> https://www.gnu.org/software/ghostscript/
>>>
>>> Both programs are distributed under the AGPL, as far as I can tell. But
>>> Artifex Ghostscript is actively developed, which I think is very
>>> important for C software that is designed to handle untrusted input.
>>
>> Thanks for bringing this up. GNU Ghostscript seemed to go
>> mostly-inactive[0] after Artifex changed to AGPL in 2013[1]. The latest
>> "upstream" release is 9.21[2], we have 9.14.0 (from 2014!).
>>
>> I'm in favor of switching to the active fork.
>
> Me too.  In fact, I once tried to package Artifex Ghostscript, but
> failed in the attempt to unbundle libraries.

Ditto.  In the discussion you mentioned above, Didier Link of
GNU Ghostscript did not really address our concerns.

Thanks,
Ludo’.

  parent reply	other threads:[~2017-05-23 20:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-20 20:55 Switching to Artifex Ghostscript Leo Famulari
2017-05-20 21:53 ` Marius Bakke
2017-05-21 13:06   ` Ricardo Wurmus
2017-05-23 17:39     ` Leo Famulari
2017-05-26 12:02       ` Ricardo Wurmus
2017-05-23 20:42     ` Ludovic Courtès [this message]
2017-05-29 17:50       ` Leo Famulari
2017-05-29 18:33         ` Leo Famulari
2017-05-29 18:38         ` Ricardo Wurmus
2017-05-29 20:47           ` Leo Famulari
2017-05-29 22:14           ` Leo Famulari
2017-06-02 16:26             ` Leo Famulari
2017-06-02 18:16               ` Leo Famulari
2017-06-03 13:55                 ` Ludovic Courtès
2017-05-29 23:22           ` Mark H Weaver
2017-05-30  4:40             ` Leo Famulari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87inkr8fui.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).