Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of fil@adobe.com designates
 64.18.1.39 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Date: Tue, 26 Mar 2013 10:55:46 -0700
Subject: Re: [cordova-cli] - config.xml handling: should that move into
 ./bin scripts?
Thread-Topic: [cordova-cli] - config.xml handling: should that move into
 ./bin scripts?
Thread-Index: Ac4qSyYlzeCdK9njTZKqTjmJ4aDvvQ==
Message-ID: <CD772EDE.1B6D5%fil@adobe.com>
In-Reply-To: 
 <CANpVHHyy7vLGGbmFjLHJgjbeC+n+UL49u94N--raVLfL5UH2cw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.2.130206
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

What if plugman worked a little more naively: on uninstall of plugin A, it
runs through all plugins and uninstalls them, then runs through and
installs all plugins except for plugin A again.

On 3/26/13 10:52 AM, "Anis KADRI" <anis.kadri@gmail.com> wrote:

>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
><braden@chromium.org>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
>> <tommy@devgeeks.org>wrote:
>>
>> > +1
>> >
>> > On 24/03/2013, at 16:52, Dave Johnson <dave.c.johnson@gmail.com>
>>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]
>> >=20
>>https://github.com/apache/cordova-android/blob/master/bin/create.js#L216
>> > >
>> > >
>> > > On Sat, Mar 23, 2013 at 7:20 PM, Filip Maj <fil@adobe.com> 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).
>> > >>
>> > >>
>> >
>>