From: Martin Jansa <martin.jansa@gmail.com>
To: Chris Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [oe-commits] Tom Zanussi : lttng2-ust: rename to lttng-ust
Date: Wed, 16 Jan 2013 19:47:59 +0100 [thread overview]
Message-ID: <20130116184759.GG3002@jama> (raw)
In-Reply-To: <CABcZANmR8vAcEFwOWBf7PdufdZTCXwWFreegpREWj99EzH1caA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]
On Wed, Jan 16, 2013 at 11:02:41AM -0700, Chris Larson wrote:
> On Wed, Jan 16, 2013 at 9:40 AM, Tom Zanussi <tom.zanussi@intel.com> wrote:
>
> > This is for the userspace tracing part, lttng-ust, which AFAIK doesn't
> > require any kernel patches.
> >
>
> Yes, but the point was, as far as I know, the newer ust requires the newer
> kernel components, and the older requires the older kernel components, so
> technically the package upgrade on a device is likely to change the
> behavior.
>
> I didn't say the current version required patches, the point was about the
> upgrade path for this recipe. I suspect we're one of the only companies
> that was actually using the old recipes, and we don't particularly care
> about the binary package upgrade paths at this time, but again, this is
> *not* a particularly smooth binary package upgrade path. I expect we're
> fine with that, but I wanted make sure it was an explicit conscious choice
> of behavior, not something unexpected.
From what you said it looks like recipe shouldn't be renamed in first
place.
I'm not interested in lttng, first I was commenting only about recipe
being renamed without RPROVIDES/RREPLEACES/RCONFLICTS combo and then I
was surprised to see that ERROR about version downgrade from
buildhistory.
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-01-16 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130116115800.A69171034D@opal>
2013-01-16 14:09 ` [oe-commits] Tom Zanussi : lttng2-ust: rename to lttng-ust Martin Jansa
2013-01-16 15:38 ` Tom Zanussi
2013-01-16 15:46 ` Chris Larson
2013-01-16 16:40 ` Tom Zanussi
2013-01-16 18:02 ` Chris Larson
2013-01-16 18:47 ` Martin Jansa [this message]
2013-01-16 19:24 ` Tom Zanussi
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=20130116184759.GG3002@jama \
--to=martin.jansa@gmail.com \
--cc=clarson@kergoth.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