From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Updating libtiff
Date: Thu, 07 Oct 2010 06:46:06 -0700 [thread overview]
Message-ID: <4CADCF1E.3090602@mentor.com> (raw)
Hey all,
I'm looking to update libtiff to cover some security issues in the
version we ship, and I noticed something funny about how we do it today.
Currently tiff_3.9.2.bb sets PV to 3.9.2+4.0.0beta5 and grabs and
builds 4.0.0beta5. While it's possible that in the past 3.9.2 was
intended to be the last 3.9.x, it wasn't.
I think we should go with:
- Add tiff_4.0.0beta6.bb which should be compatible with beta5 and will
get upgrades right.
- Add tiff_3.9.4.bb as well, in case someone wants to stay on the
released line.
Anyone see a problem with that?
--
Tom Rini
Mentor Graphics Corporation
next reply other threads:[~2010-10-07 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 13:46 Tom Rini [this message]
2010-10-07 13:54 ` Updating libtiff Holger Freyther
2010-10-07 14:00 ` Frans Meulenbroeks
2010-10-07 17:11 ` Tom Rini
2010-10-07 13:57 ` Frans Meulenbroeks
2010-10-07 14:00 ` Martin Jansa
2010-10-07 17:14 ` Tom Rini
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=4CADCF1E.3090602@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@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