ext Thiago Macieira <[email protected]> writes: > You're describing here a Store that doesn't push individual packages (.rpm) > files, but instead an installation instruction that includes adding a > repository if necessary.
Yep. If we want package management to be a platform service, then this is the way to go. > I like that. Me too. :-) > My recommendation and conclusion is then the following: I fully agree with this. > 1) packages are allowed to have dependencies that are not pre-installed on > the > device. This means the installation mechanism must have dependency resolution > enabled. (in other words, it should go through yum/zypper, not straight to > rpm) > > 2) the only repository guaranteed to be always enabled in all MeeGo devices > is > the Core profile repository > > 3) [wish] the Open Source, community repository should also be enabled on all > devices so it's an allowed source of packages too, even if it triggers a > warning that the packages there are not QA'ed > > 4) profile-specific repositories (handset, netbook, tablet, ivi, stb, etc.) > are > allowed if the vendor is aware that the package will not install on all > devices. The spec should say that this is not recommended. > > 5) use of other repositories makes it not MeeGo compliant, but is tolerated > by > use of stores. These are governed by the rules of the specific store the > application is being submitted to. > > Any third-party repository falls under rule #5, which may include someone's > personal repository, something like Extras-Testing and Extras-Devel, vendor- > specific repositories (containing overlays for things like GL drivers), etc. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
