public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Libjpeg-Turbo Drops Newer ABIs
Date: Fri, 2 Aug 2013 13:45:02 -0400	[thread overview]
Message-ID: <20130802134502.77231249f8d453dcd846063a@comcast.net> (raw)

Libjpeg-turbo has been the default jpeg image processor on Gentoo
for some time now.  But when I updated my system recently, the latest
(unstable) libjpeg-turbo-1.3.0-r2 seems to have taken a giant step
backward.  Here is the Gentoo changelog for 1.3.0-r2:

"Revert back to .so.62 with 2 functions backported from .so.8, namely
jpeg_mem_dest() and jpeg_mem_src(). ABIs .so.7 and .so.8 are dead and
shouldn't be used anywhere anymore."

This sudden change required the re-emerge of a LOT of packages.

I have not been able to find any background information on the
reason for this change.  Does anyone know the story behind this
elimination of the newer JPEG ABI's and the step back to .so.62?
Has any functionality, such as lossless cropping, been affected?

Frank Peters



             reply	other threads:[~2013-08-02 17:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02 17:45 Frank Peters [this message]
2013-08-02 18:02 ` [gentoo-amd64] Libjpeg-Turbo Drops Newer ABIs Mark Knecht
2013-08-02 18:18   ` Canek Peláez Valdés
2013-08-02 18:22     ` Rich Freeman
2013-08-02 18:28       ` Mark Knecht
2013-08-02 18:58         ` Frank Peters
2013-08-02 19:17           ` Mark Knecht
2013-08-03  7:17         ` Sergey Popov
2013-08-02 18:24     ` Mark Knecht
2013-08-02 18:40 ` Mark Knecht
2013-08-02 18:50 ` Barry Schwartz
2013-08-02 19:06   ` Frank Peters
2013-08-02 19:31     ` Barry Schwartz

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=20130802134502.77231249f8d453dcd846063a@comcast.net \
    --to=frank.peters@comcast.net \
    --cc=gentoo-amd64@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox