I totally agree that we should use auto-detection. But we could still have this package.
The package is just some configuration and data file. Actually it could be fine if auto detection could load/apply appropriate settings. We could add policy-settings-icdk(if any) into default handset build as well but only appropriate setting is loaded/applied in matching platform with the way Arjan provided Peter > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Arjan van de > Ven > Sent: Thursday, January 13, 2011 1:57 AM > To: Carsten Munk > Cc: [email protected] > Subject: Re: [meego-packaging] [meego-commits] 11924: Remove package > Trunk:Testing/policy-settings-basic-ncdk > > On 1/12/2011 9:54 AM, Carsten Munk wrote: > > 2011/1/12 Chris Ferron<[email protected]>: > >> Hi, > >> Please remove package policy-settings-basic-ncdk from project > Trunk:Testing > >> > >> Reason: This package is not appropriately named and might not be > correct. > >> having a policy settings for mfld may be ok, but not for various version of > mfld. (ie iCDK vs nCDK). > >> At very least the name is wrong. > > Out of technical curiousity, how do you tell iCDK and nCDK apart on > > run-time? > > DMI information > > kernel exposes that via sysfs in > /sys/devices/virtual/dmi/id/product_name and/or board_name > > (this is the standard IA way of enumerating what board you're on) > > _______________________________________________ > MeeGo-packaging mailing list > [email protected] > http://lists.meego.com/listinfo/meego-packaging _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
