On 9/16/2010 1:45 PM, Andrew Flegg wrote:
On Thu, Sep 16, 2010 at 21:04, Skarpness, Mark<[email protected]> wrote:
On Sep 16, 2010, at 12:49 PM, Andrew Flegg wrote:
Make compliance of a package dependent on the ability of the
repository to guarantee that all its dependencies can be met.
For Extras/Surrounds that'd be itself and the Core.
You lost me here - it sounds like we are still mandating the
availability of repositories to enable a compliant application
to run. Can you say more about how this would work?
Example, we have fooapp, bobapp, libbaz, libbar and libc.
* libc is in MeeGo Core and can be depended on by anything.
* libbaz is in MeeGo Extras, depends on libc and is
Compliant.
* libbar is in MeeGo Extras. It depends on libbaz and is
ALSO Compliant, because it is in Extras; and since
it can only be got from Extras, the thing retrieving it
must be able to get libbaz as well.
* fooapp is in MeeGo Extras. It depends on libbar and is
ALSO Compliant, for the same reasons as libbar.
* bobapp also depends on libbar. It's in Ovi Store.
this is where you get in trouble if vendor Z ships libbar but in a
different configuration/version for some widgety nifty thing that they do...
... and that version/configuration is not ABI compatible.
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
