Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Marko Lindqvist <cazfi74@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: libpng-1.5.13
Date: Thu, 06 Dec 2012 10:26:22 -0800	[thread overview]
Message-ID: <50C0E34E.8010108@linux.intel.com> (raw)
In-Reply-To: <1354740033-18500-1-git-send-email-cazfi74@gmail.com>

On 12/05/2012 12:40 PM, Marko Lindqvist wrote:
>
> First preparatory patch makes it easier to add multiple major versions of
> libpng. You may choose to commit this one only.
>
> Second patch adds 1.5.13 recipe. This produces library named libpng15, while
> old 1.2.50 recipe produces libpng12. Some older programs (and their recipes)
> may fail to find newer library. So far I'm aware of one such case in
> meta-openembedded; libsdl-image-1.2.10 needs update. I've already submitted
> patch for that one.
>
Overall, it's great to see the recipes updated, but we don't typically 
keep the older versions of recipes around.  So if you want to preserve 
the older version, it should be moved meta-oe.  The only case we keep 
older recipes is for License changes from GPLv2 -> GPLv3 where it makes 
sense.

So, the request would be a v2 that also removes the 1.2.50 recipe.

Thanks
	Sau!

> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>



  parent reply	other threads:[~2012-12-06 18:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05 20:40 libpng-1.5.13 Marko Lindqvist
2012-12-05 20:40 ` [PATCH 1/2] libpng: split recipe to libpng.inc and libpng_1.2.50.bb Marko Lindqvist
2012-12-05 20:40   ` [PATCH 2/2] libpng: add 1.5.13 recipe Marko Lindqvist
2012-12-06 18:26 ` Saul Wold [this message]
2012-12-07 13:30   ` libpng-1.5.13 Marko Lindqvist
2012-12-08 22:43   ` libpng-1.5.13 Scott Garman

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=50C0E34E.8010108@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=cazfi74@gmail.com \
    --cc=openembedded-core@lists.openembedded.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