[oe] [RFC] gnome.bbclass change broke lots of package dependencies

Phil Blundell pb at reciva.com
Mon May 25 10:20:22 UTC 2009


On Mon, 2009-05-25 at 12:07 +0300, Ihar Hrachyshka wrote:
> @@ -17,6 +17,9 @@ inherit autotools gtk-icon-cache pkgconfig gconf mime
> 
>  AUTOTOOLS_STAGE_PKGCONFIG = "1"
> 
> +PACKAGES =+ "${PN}-scrollkeeper-leftovers"
> +FILES_${PN}-scrollkeeper-leftovers = "${localstatedir}/lib/scrollkeeper"
> +
>  gnome_stage_includes() {
>         autotools_stage_includes
>  }
> 
> As we can see, there is now ${PN}-scrollkeeper-leftovers package for
> every recipe that inherited gnome.bbclass. And this -leftovers package
> is in the current dependency chains (at least for qt4-embedded-dev
> package).

Where is your dependency on -scrollkeeper-leftovers coming from?
Nothing in the patch that you quoted looks like it ought to be causing
that.

That said, the patch does look a bit bizarre: as a general rule we don't
package things from ${localstatedir} since lots of targets have that as
a ramdisk.  It isn't obvious to me what this is going to achieve.

> As for the 1st problem, I suggest adding ALLOW_EMPTY = "1" to
> gnome.bbclass (it works for my current setup, and if you will approve
> the change then I'll send the patch immediately).

No, this would be a poor solution since it will cause a mass of empty
(and hence useless) packages to be generated.  It would be better to
identify the place where the dependency on this package is generated,
and suppress that at its source if the package is empty.

> As for the 2nd problem, there is a big question what should we do.
> Revision bumping for every recipe that inherits gnome.bbclass is not
> an elegant thing (though it will really push the change for all the
> users). Maybe there is another, better way to handle such tasks. If
> you know it please provide me with the info.

The right answer to this probably depends on the answer to what the
patch was trying to accomplish in the first place.  It's possible that
no rebuild is actually necessary for already-deployed packages if this
is intended to deal with some fringe case that only occurs on particular
targets or under rare circumstances.

p.






More information about the Openembedded-devel mailing list