Backward is if we always have platform independent policy-settings-platform-independent installed as default fallback (which means /usr/share/policy/rules/current/policy.plc always exist on any platform). There will be a potential confliction with policy-settings-*. For policy-settings-mfld policy-settings-tablet, it's fine because we can install /usr/share/policy/rules/current/**-policy.plc, and could use boardname in rc.sysinit to guide ohmd to find it.
But for policy-settings-n900, I'm not sure if it is going to change to install something like n900-policy.plc, and I'm also not sure if n900 has boardname package to guide ohmd on N900 to find correct configuration. Any comments? Thanks! -----Original Message----- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Zheng, Huan Sent: Friday, April 22, 2011 1:01 PM To: Shane Bryan Cc: meego-dev; Hofemeier, Ulf; meego-packaging Subject: Re: [MeeGo-dev] [meego-packaging] policy-settings-basic-mfld moved to backup:revert project This is similar to the problem that we want to load different OHMng modules on different platforms. To accomplish this, a new environment variable is introduced, OHM_CONF_MODULE rc.sysinit checks whether /etc/boardname exists, if exist, OHM_CONF_MODULE is exported, ohmd also checks this environment variable, if exists, it will use specific **modules.ini to load different modules, it not, default modules.ini will be used. Back to this topic, we may change OHM_CONF_MODULE to OHM_CONF_PLATFORM. And this variable will lead plug-ins to find platform specific configure file(for ohm-plugin-resolver in this case, a platform specific configure file will lead to platform specific policy file); if not set, default configure file will be used. This may bring the advantage that a platform independent policy-settings-platform-independent may coexist with platform specific policy-settings-**, thus may fulfill what Shane and Joel are requesting for. Above is my idea on this, if there's no other advices, I will file a bug and implement the idea. -----Original Message----- From: Shane Bryan [mailto:shane.br...@linux.intel.com] Sent: Friday, April 22, 2011 10:45 AM To: Zheng, Huan Cc: Clark, Joel; meego-packaging; meego-dev; Hofemeier, Ulf Subject: Re: [MeeGo-dev] [meego-packaging] policy-settings-basic-mfld moved to backup:revert project On Fri, 22 Apr 2011 10:07:06 +0800 "Zheng, Huan" <huan.zh...@intel.com> wrote: > Hi, Joel > There's a misunderstanding here, policy-settings-* does not affect > pulseaudio daemon, it just affects ohmd daemon. Ohmd *must* start > with a set of prolog rules which are part of policy-settings-* > package. :) But to clarify, a missing policy-settings-* that breaks ohmd *DOES* in fact break tests for specific audio use cases across the platform, not just dialers ability to handle calls and ringtones. So I do agree with Joel here in principle that there ought to be a fallback/default package such that ohmd does not break when a platform specific on is missing. Specifically, the meego-core.xml[1] pattern file includes both ohm-plugin-ruleengine and ohm-plugin-resolver, both of which contain configuration files that expect the file /usr/share/policy/rules/current/policy to exist. This file is installed by the policy-settings-* packages, yet neither ohm-plugin-ruleengine or ohm-plugin-resolver can actually be marked to "Require:" any of the policy-settings-* packages because that would pull platform specific packages into every image created, and I don't think we even know *which* one would be pulled in since they are all in the same repos (and all "Provide: policy-settings" as a generic capability). This is a problem that is begging for a harder/deeper look by the MeeGo Release Engineering team, IMHO. Shane... [1]https://meego.gitorious.org/meego-os-base/package-groups/blobs/master/patterns/meego-core.xml _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
