Address competition between native and html apps

Description

As part of , we are building HTML applications that have the same purpose as existing native apps.

Some of them won't have any problems (e.g. two HVAC would show up in the launcher), but the homescreen and launcher can have trouble, e.g. only one app can use the homescreen layer, or when these applications auto-start we don't know which one will finally show up.

Environment

None

Activity

Show:

Jan-Simon Moeller September 12, 2019 at 9:47 PM

Live example to look at: https://gerrit.automotivelinux.org/gerrit/#/c/AGL/meta-agl-devel/+/22408/   (virtual/voiceagent)

Stephane Desneux September 12, 2019 at 10:18 AM

+1

Jacobo Aragunde Pérez September 12, 2019 at 7:36 AM

This suggestion comes from Jan-Simon:

the competition in the recipes is easily expressed by using the
virtual/<somename> construct (bitbake 'Virtual Providers').

Both packages will declare to
PROVIDES_${PN} += "virtual/<somename>"

The packagegroup pulls in virtual/<somename> instead.
Then we can define a PREFERRED_PROVIDER_virtual/<somename> = "abc" .

That solves the yocto side of things at least.

Won't Fix

Details

Assignee

Jacobo Aragunde Pérez

Reporter

Labels

Priority

Created September 12, 2019 at 7:35 AM
Updated April 7, 2021 at 8:02 PM
Resolved April 6, 2021 at 12:08 PM
Loading...