From: John Darrington <john@darrington.wattle.id.au>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/2] ImageMagick 7
Date: Fri, 13 Jan 2017 06:13:41 +0100 [thread overview]
Message-ID: <20170113051341.GA8207@jocasta.intra> (raw)
In-Reply-To: <20170112221103.GA19048@jasmine>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
On Thu, Jan 12, 2017 at 05:11:03PM -0500, Leo Famulari wrote:
On Wed, Jan 11, 2017 at 03:18:38PM -0500, Leo Famulari wrote:
> So, I think we should carefully check each package that uses ImageMagick
> directly to see if they are ready. We can check their commit logs and
> bug trackers for anything related to ImageMagick.
> name: a2ps
a2ps uses the `convert` program from ImageMagick, and its use pre-dates
ImageMagick 7.
> name: awesome
Awesome also uses `convert`, and this code is from 2009.
So, they need to stay with ImageMagick 6 for now.
So far as I'm aware, the "convert" program's interface has not changed between 6 and 7
so unless we know of a particular problem, I don't see why they could not move to vers
7 immediately.
J'
--
Avoid eavesdropping. Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-01-13 5:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 19:37 [PATCH 0/2] ImageMagick 7 Leo Famulari
2017-01-09 19:37 ` [PATCH 1/2] gnu: Update imagemagick to version 7.0.4-3 Leo Famulari
2017-01-09 19:37 ` [PATCH 2/2] gnu: Add imagemagick-6 Leo Famulari
2017-01-09 23:03 ` [PATCH 0/2] ImageMagick 7 Ludovic Courtès
2017-01-09 23:19 ` Leo Famulari
2017-01-11 20:18 ` Leo Famulari
2017-01-12 22:11 ` Leo Famulari
2017-01-13 5:13 ` John Darrington [this message]
2017-01-13 7:34 ` Leo Famulari
2017-03-11 17:34 ` 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=20170113051341.GA8207@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).