public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: ImageMagick 6 vs 7
Date: Mon, 04 Sep 2017 22:38:00 -0000	[thread overview]
Message-ID: <9bebcb64-6be2-06e3-7bba-60bb2d3debd5@cygwin.com> (raw)
In-Reply-To: <a5f42dbc-91de-9729-e639-19dffe0f9e15@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1074 bytes --]

On 2017-09-04 15:03, Marco Atzeri wrote:
> On 04/09/2017 21:52, Yaakov Selkowitz wrote:
>> A recent discussion on Fedora's devel list has brought to my attention
>> that ImageMagick 7 would be incompatible with 6 not only wrt API/ABI but
>> also wrt CLI (affecting scripts etc.).  It would seem prudent to stick
>> with the 6 series for the time being until the Linux distributions sort
>> this out.
>>
>> If you concur, would you mind updating ImageMagick to the latest 6.9
>> release?  It seems to be somewhat behind at the moment.
> 
> I was not planning to move to 7.x for the time being.

Probably for the best.

> I will look on latest 6.9 but I had the impression they bumped
> the API in anycase.

Yes, but it sounds like that shouldn't require more than a customary
rebuild of the few packages which use libMagick{Core,Wand}6.

> It is the worst package as stability that I am aware...

It's definitely among the worst.  I do wonder if at least 6 will settle
down ABI-wise with 7 out, but given their history, who knows.

-- 
Yaakov


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2017-09-04 22:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-04 19:52 Yaakov Selkowitz
2017-09-04 20:04 ` Marco Atzeri
2017-09-04 22:38   ` Yaakov Selkowitz [this message]
2017-09-06 12:29     ` Marco Atzeri

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=9bebcb64-6be2-06e3-7bba-60bb2d3debd5@cygwin.com \
    --to=yselkowitz@cygwin.com \
    --cc=cygwin-apps@cygwin.com \
    /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.
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).