From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Chris Larson <clarson@kergoth.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v3] libjpeg: Replace libjpeg with libjpeg-turbo
Date: Tue, 8 Dec 2015 00:09:12 +0100 [thread overview]
Message-ID: <20151207230912.GD2249@jama> (raw)
In-Reply-To: <CAJTo0LZmao029oQMnK8=5tOZn0FPkAzvCjez-CkOCNG_oCY7rw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
On Mon, Dec 07, 2015 at 10:56:48PM +0000, Burton, Ross wrote:
> On 2 December 2015 at 07:56, Maxin B. John <maxin.john@intel.com> wrote:
>
> > meta/recipes-core/jpeg/jpeg_9a.bb | 29 -------------------
> > meta/recipes-core/jpeg/libjpeg-turbo_8d+1.4.2.bb | 36
> > ++++++++++++++++++++++++
> >
>
> (CCing the usual suspects who will notice and care about this)
>
> I've just noticed that this means that when the binary packages are
> debian-renamed the version goes backwards: libjpeg-9a to libjpeg-8d+1.4.2.
> Does anyone have an opinion on either:
>
> 1) ignore it
I'm ok with ignoring it, because all DISTROs I care about were always
using libjpeg-turbo.
> 2) put an PE (epoch) in libjpeg-turbo
> 3) configure the debian renaming so the library has a different name
> (libjpeg-turbo, presumably)
>
> Ross
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-12-07 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 7:56 [PATCH v3] libjpeg: Replace libjpeg with libjpeg-turbo Maxin B. John
2015-12-02 12:56 ` Otavio Salvador
2015-12-02 8:39 ` Maxin B. John
2015-12-04 9:11 ` Burton, Ross
2015-12-04 6:03 ` Maxin B. John
2015-12-04 10:58 ` Burton, Ross
2015-12-07 22:56 ` Burton, Ross
2015-12-07 23:09 ` Martin Jansa [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-02 8:39 Maxin B. John
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=20151207230912.GD2249@jama \
--to=martin.jansa@gmail.com \
--cc=clarson@kergoth.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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 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.