[OE-core] [PATCH] alsa-lib: remove non PN based -dev packages

[Huang, Jie (Jackie)]

> 
> Op 28 jul. 2014, om 08:49 heeft Huang, Jie (Jackie) <Jackie.Huang at windriver.com> het volgende
> geschreven:
> 
> >
> >
> >> -----Original Message-----
> >> From: Koen Kooi [mailto:koen at dominion.thruhere.net]
> >> Sent: Monday, July 28, 2014 2:30 PM
> >> To: Huang, Jie (Jackie)
> >> Cc: OE-core; Richard Purdie
> >> Subject: Re: [OE-core] [PATCH] alsa-lib: remove non PN based -dev
> >> packages
> >>
> >>
> >> Op 25 jul. 2014, om 12:05 heeft jackie.huang at windriver.com het volgende geschreven:
> >>
> >>> From: Jackie Huang <jackie.huang at windriver.com>
> >>>
> >>> All dev related items should be packaged in the core PN-dev package
> >>> not in seperate packages.
> >>
> >> What's the upgrade path here for image and users that have 'alsa-dev'
> >> installed? Looks like there are
> >
> > My patch is removing 'alsa-dev' and all related files goes into
> > '${PN}-dev' (PN=alsa-lib here), so users need to install alsa-lib-dev instead of alsa-dev.
> 
> *sigh* So you have no upgrade path for situations where 'alsa-dev' is already installed or listed in a
> packagegroup or image. Worse, you don't even understand the problem :/

I see your point, I did grep on oe-core and meta-oe and didn't find any evidence that 'alsa-dev' is installed or listed
In a packagegroup or image, so I thought it's safe to remove without RREPLACES/RPROVIDES in place, sorry that I did
a wrong assumption, I will add a RPROVIDES for this, thanks!

Thanks,
Jackie

> 
> >
> >> now 2 conflicting packages, 'alsa-dev' in the feeds and
> >> 'alsa-lib-dev' on OE, without and
> >
> > Only 'alsa-lib-dev' now with my patch, so no conflicts.
> 
> Hahahahahaha you are really funny.