[MeeGo-dev] Meego spec - for comment

[Andrew Flegg]

Thiago wrote:
> 
> If you're not using a store application, but a simple .rpm on your
> website,   then you cannot rely on end-users figuring out dependencies.
> You should only   depend on what's available on the core repositories,
> which are always enabled   in all devices. This includes web-only stores,
> like the Ovi Store was/is for   Maemo5.

Why do we keep omitting community repositories, of which there should be a meego.com one (seeded by the MeeGo Community OBS), or indeed any third party repo?

The rule could be worded as:

  "No MeeGo-compliant package can depend on a
   package which is not contained in the baseline
   or available to the user from the repository
   in which the package is retrieved."

I think we should stop thinking in terms of the package as a unit, and instead think of the repo. It then becomes a process issue to make sure that unstable or invalid packages don't make it in (c.f. maemo.org Extras process).

Cheers,

Andrew

-- 
Andrew Flegg -- mailto:andrew at bleb.org   |   http://www.bleb.org/
Maemo Community Council chair