[oe] [PATCH 1/3] libnotify3: remove the recipe

[Paul Eggleton]

On Thursday 27 August 2015 12:49:27 Andreas Müller wrote:
> On Thu, Aug 27, 2015 at 10:23 AM, Paul Eggleton
> 
> <paul.eggleton at linux.intel.com> wrote:
> > On Wednesday 26 August 2015 20:01:28 Andreas Müller wrote:
> >> On Wed, Aug 26, 2015 at 12:59 PM, Alexander Kanavin
> >> 
> >> <alexander.kanavin at linux.intel.com> wrote:
> >> > On 08/26/2015 01:40 PM, Tanu Kaskinen wrote:
> >> >>>   # needs libnotify3 which conflicts with libnotify, mixing them in
> >> >>>   build
> >> >>> 
> >> >>> breaks couple of packages
> >> >> 
> >> >> This last comment seems to be out of date after this patch.
> >> > 
> >> > Actually, this whole thing can be removed:
> >> > 
> >> > # needs libnotify3 which conflicts with libnotify, mixing them in build
> >> > breaks couple of packages
> >> > EXCLUDE_FROM_WORLD = "1"
> >> > 
> >> > Whoever applies this patch, please amend it accordingly.
> >> > 
> >> > 
> >> > Alex
> >> 
> >> I think it's not that easy. We need an libnotify append here with some
> >> RREPLACES / RPOVIDES for libnotify3. Right?
> > 
> > I was wondering about that myself. Really those RREPLACES + RPROVIDES +
> > RCONFLICTS need to go into the recipe in OE-Core though.
> 
> Sorry to insist: I think it should be appended here: Users without
> meta-gnome in their layers have never seen libnotify3.

Does it matter? Adding these alone to the core recipe won't have any effect if 
you've never seen it before; and we do have precedents for this kind of thing.

In general I strongly believe that "software-only" layers such as the ones in 
meta-openembedded should not have any bbappends (with the possible exception 
of toolchain-layer, assuming that's even still used) - the reason being, you 
should be able to add any of those layers to your configuration and have 
confidence that you won't experience any unexpected effects in your build. 
Adding RPROVIDES/RREPLACES/RCONFLICTS isn't exactly going to break the world, 
I agree, but at the very least it will trigger repackaging of libnotify if it 
has already been built, which will also trigger repackaging of any other 
dependent recipes; you might not expect that to happen just by adding the 
layer to your bblayers.conf. That's what I'd like to avoid.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre