Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Colin Walters <walters@verbum.org>
Cc: Burton, openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gdk-pixbuf: Fix libpng determinism issues
Date: Sun, 14 Apr 2013 16:33:16 +0100	[thread overview]
Message-ID: <1365953596.8670.9.camel@ted> (raw)
In-Reply-To: <1365944532.5651.12.camel@localhost>

On Sun, 2013-04-14 at 09:02 -0400, Colin Walters wrote:
> Is "libpng" the new canonical name for 1.6?

Its a symlink to libpng16.pc which is something libpng upstream's "make
install" provides.

>   I assume there was a reason
> it was listed last.  It looks like the current logic came from:
> 
> https://git.gnome.org/browse/gdk-pixbuf/commit/?id=ddedf5a2c2c63bfe8d6f04376cf2bba215a5eb19
>
> Which is a not very enlightening commit message.  It looks like the
> Fedora 18 "libpng" package provides both libpng.pc and libpng15.pc.
> RHEL6 has the same except it's libpng12.pc too.  My Ubuntu 12.10 VM has
> libpng12 with just libpng12.pc, no libpng.pc.

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.

> My main concern with this patch was ensuring that people aren't getting
> a suddenly ancient and deprecated libpng, but that seems unlikely, so
> unless there are other comments I can take care of turning this into
> "git format-patch" style and pushing upstream.

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. 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.

Cheers,

Richard




  reply	other threads:[~2013-04-14 15:51 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 [this message]
2013-04-15 10:08     ` Colin Walters
2013-04-15 10:14       ` Koen Kooi
2013-04-15 11:31       ` Richard Purdie
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=1365953596.8670.9.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --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