[OE-core] [oe-commits] Tom Zanussi : lttng2-ust: rename to lttng-ust

[Tom Zanussi]

On Wed, 2013-01-16 at 19:47 +0100, Martin Jansa wrote:
> 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 at 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.
> 

You may be right and what's confusing things is that the new name of the
lttng project actually includes the version number as part of its name
despite it being a completely new project.

So I could submit a patch to rename lttng-ust back to lttng2-ust, but
that would be inconsistent with the other packages in 'lttng2' - it
would in that case make sense to rename them also to lttng2-prefixed
versions i.e. lttng2-modules, lttng2-tools.   It does get kind of
awkward when lttng2 releases a version 3  though- we'd have an
lttng2_ust_3.0 then.  Or will we just rename everything to lttng3_* at
that point, which if the lttng project doesn't do the same, means we'd
have provide some kind of mapping to say that our lttng3 is actually
lttng 2.0's 3.0 and so on...

Or we could just keep everything as lttng-*, rename the lttng2-ust now
and just keep it that way in future regardless of what lttngX decides to
name itself next time.

I'm happy to do either, depending on what people want..

Tom

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