public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [Fwd: ImageMagick update to 6.9.0-9. So-name bump: libMagick++-6.Q16.so.3 -> libMagick++-6.Q16.so.6]
Date: Sat, 30 May 2015 16:33:00 -0000	[thread overview]
Message-ID: <5569E641.7040804@gmail.com> (raw)
In-Reply-To: <54F83925.2090305@gmail.com>



On 3/5/2015 12:08 PM, Marco Atzeri wrote:
> On 3/5/2015 5:36 AM, Yaakov Selkowitz wrote:
>> Marco,
>>
>> Well, that didn't take long, see attached.  (Not that I'm surprised,
>> given their history.)  Before you update ImageMagick to upstream
>> 6.9.0-9, you'll need to (re)build the current release (or a newer one
>> prior to 6.9.0-9) and split the DLLs into libMagickCore6_2 (which
>> OBSOLETES libMagickCore6), libMagickWand6_2, and libMagick++6_3.  The
>> latter will then become libMagick++6_6 after the 6.9.0-9 version bump.
>>
>> --
>> Yaakov
>>
>
> Noted.
> Low priority for the time being for a update of ImageMagick.
>
> I am almost ready for the double uplode of GraphicsMagick
>
> 1.3.20-3 for splitting the libs as discussed and
> 1.3.21-1 for bumping the C++ ABI (3 -> 11)
>
> I want just to make some extra check to avoid breaking something more
> as I will be on the road/air for the next 2 weeks.
>
> Regards
> Marco
>

I am uploading 6.9.1.3-1 as test for the Perl rollout.

  libMagickCore6_2
  libMagickC++6_6
  libMagickWand6_2

No changes for MagickGraphics test 1.3.21-2

  libGraphicsMagick3
  libGraphicsMagickWand2
  libGraphicsMagick++11


Regards
Marco






      reply	other threads:[~2015-05-30 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05  4:36 Yaakov Selkowitz
2015-03-05 11:08 ` Marco Atzeri
2015-05-30 16:33   ` Marco Atzeri [this message]

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=5569E641.7040804@gmail.com \
    --to=marco.atzeri@gmail.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).