Yeah. I've talking about that specific problem with one of the PhoneGap::Build guys. It's not easy. It is also not limited to permissions but to every possible configuration entry including configuration that has runtime variables in them (package names, api keys, etc...). The easy and obvious solution would be to not delete configuration entries and leave it up the to user but it's definitely not the cleanest solution ;-)
On Mon, Mar 25, 2013 at 7:17 AM, Braden Shepherdson <[email protected]>wrote: > Permissions require more clever handling than naive XML injection. I'll be > talking about that somewhat later. Permissions on Android need de-duping, > and making sure that deleting one plugin that requires permission X doesn't > remove that permission if another plugin still needs it. > > Braden > > > On Sun, Mar 24, 2013 at 2:57 AM, tommy-carlos Williams > <[email protected]>wrote: > > > +1 > > > > On 24/03/2013, at 16:52, Dave Johnson <[email protected]> wrote: > > > > > it would make sense to have a separate project-level script that would > > (for > > > android for example) contain stuff like setting the activity name > rather > > > than doing it all in create [1]. Ideally it would enable changing of > app > > > package/id etc in an already existing project too. > > > > > > [1] > > https://github.com/apache/cordova-android/blob/master/bin/create.js#L216 > > > > > > > > > On Sat, Mar 23, 2013 at 7:20 PM, Filip Maj <[email protected]> wrote: > > > > > >> > > >>> In the future when we ship without core plugins it should also, on > > android > > >>> at least, add appropriate permissions for the various plugins. > > >> > > >> This is already handled by the plugin.xml spec, where you can attach > > >> arbitrary xml to any xml document that is platform-specific (such as > > >> android manifest). > > >> > > >> > > >
