From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Updating libtiff
Date: Thu, 7 Oct 2010 16:00:16 +0200 [thread overview]
Message-ID: <20101007140016.GC3163@jama> (raw)
In-Reply-To: <4CADCF1E.3090602@mentor.com>
On Thu, Oct 07, 2010 at 06:46:06AM -0700, Tom Rini wrote:
> 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?
Isn't PV="4.0.0" < PV="4.0.0beta5"?
Then it would be better to stay with 3.9.2+4.0.0beta* sheme for easy
upgrade path to 4.0.0 release.
at least that's the reason why I have ie:
KERNEL_RELEASE = "2.6.36-rc7"
OLD_KERNEL_RELEASE = "2.6.35"
PV = "${OLD_KERNEL_RELEASE}+${KERNEL_RELEASE}+gitr${SRCPV}"
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2010-10-07 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 13:46 Updating libtiff Tom Rini
2010-10-07 13:54 ` 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 [this message]
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=20101007140016.GC3163@jama \
--to=martin.jansa@gmail.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 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.