From: Tej Chajed <tchajed@mit.edu>
To: 25967@debbugs.gnu.org
Subject: bug#25967: 25.1; Support for ImageMagick 7
Date: Sat, 4 Mar 2017 11:17:41 -0500 [thread overview]
Message-ID: <6a48dc20-17fc-4e4b-b793-4c37c6bcbcc5@Spark> (raw)
[-- Attachment #1: Type: text/plain, Size: 587 bytes --]
Are there plans to upgrade from ImageMagick 6 to 7? I ask because I’m fixing imagemagick support for the Emacs formula in Homebrew (pull #10477) and Homebrew has to depend on the legacy ImageMagick 6 to build Emacs with ImageMagick support.
It looks like there was a brief discussion on emacs-devel about this in a thread about the 64-bit Windows build, where the belief was that ImageMagick 7 is too unstable to use. If this is indeed the case it makes sense to stick with ImageMagick 6 but I don’t think there was much of an explicit discussion about upgrading in that thread.
[-- Attachment #2: Type: text/html, Size: 994 bytes --]
next reply other threads:[~2017-03-04 16:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 16:17 Tej Chajed [this message]
2017-03-10 19:03 ` bug#25967: 25.1; Support for ImageMagick 7 Paul Eggert
2017-07-24 16:41 ` Glenn Morris
2017-07-24 22:15 ` Paul Eggert
2017-07-25 1:25 ` Glenn Morris
2017-09-02 13:06 ` Eli Zaretskii
2017-09-03 1:10 ` Glenn Morris
2017-12-12 16:59 ` Glenn Morris
2017-12-12 17:15 ` Marcin Borkowski
2017-12-12 17:44 ` Glenn Morris
2018-06-01 19:17 ` bug#25967: [PATCH] Add support for ImageMagick 7 (Bug#25967) Karl Otness
2018-06-23 10:09 ` Kévin Le Gouguec
2018-06-25 21:08 ` Karl Otness
2018-08-28 2:10 ` Glenn Morris
2018-08-28 20:32 ` Karl Otness
2018-08-30 18:00 ` Glenn Morris
2018-08-30 21:53 ` Karl Otness
2018-08-29 3:21 ` Karl Otness
2018-09-03 22:57 ` Andy Moreton
2018-09-04 17:11 ` Eli Zaretskii
2018-09-04 19:03 ` Andy Moreton
2018-09-05 2:38 ` Eli Zaretskii
2018-08-28 2:12 ` bug#25967: 25.1; Support for ImageMagick 7 Glenn Morris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a48dc20-17fc-4e4b-b793-4c37c6bcbcc5@Spark \
--to=tchajed@mit.edu \
--cc=25967@debbugs.gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.