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.
Imagine that Nokia ship Extras and Ovi enabled in all their devices.
bobapp is in Ovi, and can be in MeeGo Compliant as only Nokia devices
can have Ovi and all Nokia devices have Extras available and enabled
to provide their dependencies.
However, if the bobapp developer uploaded the package to another repo,
it may not be Compliant, as the covenant that it's dependencies MUST
be resolvable isn't met. Then, the developer would have to upload the
source packages (or binary) from Extras to that third party repo as
well; or link them in statically.
Hope that helps,
Andrew
--
Andrew Flegg -- mailto:[email protected] | http://www.bleb.org/
Maemo Community Council chair
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
