From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Colin Walters <walters@verbum.org>
Cc: Burton, mclasen@redhat.com,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gdk-pixbuf: Fix libpng determinism issues
Date: Mon, 15 Apr 2013 12:31:44 +0100 [thread overview]
Message-ID: <1366025504.8670.30.camel@ted> (raw)
In-Reply-To: <1366020508.2896.16.camel@localhost>
On Mon, 2013-04-15 at 06:08 -0400, Colin Walters wrote:
> On Sun, 2013-04-14 at 16:33 +0100, Richard Purdie wrote:
> > On Sun, 2013-04-14 at 09:02 -0400, Colin Walters wrote:
> > The more interesting change is:
> >
> > https://git.gnome.org/browse/gdk-pixbuf/commit/configure.ac?id=d430bc4df3314a88cd538474d26ff7764d1f408c
> >
> > and following that to the bugzilla 'For this to make sense, I changed
> > the order so that a version specific dep, such as libpng15 or
> > libpng12,
> > is found before just "libpng".'
> >
> > I'm not sure I entirely follow that logic.
>
> I added Matthias to CC as he touched this last then.
>
> > I think the intent of the symlink is to provide the system with a
> > default libpng to use in the absence of a specific version requirement.
> > As the code stands today, each time a new libpng comes out, gdk-pixbuf
> > will need changes before it will be able to use it.
>
> Right, we need configure.ac changes, but the rationale behind that is
> that we'd also need *code* changes for each new major version of libpng.
> But it sounds like what you're saying is that gdk-pixbuf compiles and
> operates correctly with 1.6? If that's the case, then the least
> invasive change here is to simply add 1.6.
It compiles and operates correctly as far as we can tell, yes.
Given that rationale, I'd suggest "libpng" should be dropped from the
list.
> Blah, I tried changing the gnome-ostree build to fetch libpng's v1.6.1
> git tag to test, but it hard requires Automake 1.13.
>
> Anyways, if it works (looks like the latest oe-core has it), then
> what about the attached?
It will make our builds work again for now until the next time someone
upgrades libpng and and then it will potentially silently start using an
old version in some builds :(.
We're therefore probably going to get stuck carrying a patch for
this :/.
> > In the meantime, it
> > will potentially link against something old, e.g. 1.2, since 1.2 is in
> > the LSB 4.X spec so most LSB like systems would have 1.6 and 1.2.
> >
> > If we can justify changing this upstream, that would be great :). It may
> > be worth adding libpng16 into the list too so everything is covered too.
>
> At this point I'm hoping the parade of libpng versions will
> settle down, so hopefully no further tweaking of the configure script or
> code will be required...
Its the case things silently break that really worry me.
Cheers,
Richard
next prev parent reply other threads:[~2013-04-15 11:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 10:25 [PATCH] gdk-pixbuf: Fix libpng determinism issues Richard Purdie
2013-04-14 13:02 ` Colin Walters
2013-04-14 15:33 ` Richard Purdie
2013-04-15 10:08 ` Colin Walters
2013-04-15 10:14 ` Koen Kooi
2013-04-15 11:31 ` Richard Purdie [this message]
2013-04-15 12:12 ` Colin Walters
2013-04-15 12:22 ` Richard Purdie
2013-04-15 12:59 ` Colin Walters
2013-04-19 12:59 ` Richard Purdie
2013-04-19 13:41 ` Koen Kooi
2013-04-19 17:17 ` Colin Walters
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=1366025504.8670.30.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=mclasen@redhat.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=walters@verbum.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