Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of alunny@gmail.com designates
 209.85.223.175 as permitted sender)
MIME-Version: 1.0
Reply-To: alunny@gmail.com
In-Reply-To: 
 <CAM-DUcO6in=qpsy6ec7ouRbFzq_4_=JHSycGmFXUz+k2K6f=uQ@mail.gmail.com>
References: 
 <CAM-DUcM2VGkmPg-n2fU8e9dp9Ti0U84VnN=UNVA9Jqi8QhkGUA@mail.gmail.com>
	<CC90B70E.F195%fil@adobe.com>
	<CAM-DUcM5BxPGw0X1Q8NohTqZemi4Hu8tuoxSDEE-epFzcO64AQ@mail.gmail.com>
	<CADVgkyOEW2Gk8LGMczKuHHb0TjDAU1kbCyYaMXGx44QacfS2rw@mail.gmail.com>
	<CACAoQH2WDVkw_KrT-hNDAjmWPgG4f7j9uSXVLuXJh411nCSczQ@mail.gmail.com>
	<CAM-DUcO6in=qpsy6ec7ouRbFzq_4_=JHSycGmFXUz+k2K6f=uQ@mail.gmail.com>
Date: Tue, 9 Oct 2012 16:44:57 -0700
Message-ID: 
 <CAPihERRjb454Cvhv=aPBGCEbOpcCvPRxbckTstqoMpjcf5_0Mw@mail.gmail.com>
Subject: Re: Pluginstall tool discussion
From: Andrew Lunny <alunny@gmail.com>
To: callback-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=14dae9399dc7fdd4aa04cba8ec37

--14dae9399dc7fdd4aa04cba8ec37
Content-Type: text/plain; charset=ISO-8859-1

I've missed most of this discussion, but I wanted to make a few quick
points:

* `pluginstall` (the tool I developed, that is used by PhoneGap Build) is a
tool for installing plugins. Per the Unix philosophy, it doesn't and won't
do anything other than that.

* There may well be a need and a demand for a tool that grabs plugins from
git repositories, uninstalls plugins, generates starter plugins, etc. But
that's not pluginstall, and I think that tool should probably be named
something else. It looks like Mike has made a start on that with his
cordova-pluginrepo repository, which is awesome.

* The problems that need to be solved by pluginstall are of the form "I
can't install plugin x with pluginstall", or "I can't write a plugin that
does x that can be installed by pluginstall." The only way to find those
problems is to try writing those plugins. The PGB team is moving forward on
a few, and we've worked with some other companies who have helped us see
where pluginstall was lacking (adding multiple children to an Android
intent-filter, installing a dylib into an iOS project).

* node-xcode is a separate project, and will be useful for any plugin tools
written with node. It would probably be better for everyone's sanity if
there was a single version of that parser. I've been pretty slack about
merging changes, so I'll get up to speed on that.

* If other tools want to interoperate with pluginstall, they should follow
the plugin spec here:
https://github.com/alunny/cordova-plugin-spec
That's a working document and is open to changes. Again, my preference is
for changes of the form "I can't write a plugin that does X in this format"
rather than "this element has a slightly misleading name; how about this
name?". The GitHub issues for that repo is the best place to discuss
changes to that spec.

Cheers,
Andrew

On 6 October 2012 09:08, Mike Reinstein <reinstein.mike@gmail.com> wrote:

> Andrew's is the one used by pg build. Anis has changes from all of us and
> has the most the up to date code:
>
> https://github.com/imhotep/pluginstall
>
> -Mike
>
>
>
> On Sat, Oct 6, 2012 at 8:08 AM, Patrick Mueller <pmuellr@gmail.com> wrote:
>
> > On Sat, Oct 6, 2012 at 5:22 AM, Brian LeRoux <b@brian.io> wrote:
> >
> > > Think its time we nominated a canonical repo for this. Fil's?
> > >
> >
> > URL please?  Are we talking about forks of pluginstall?
> >
> > --
> > Patrick Mueller
> > http://muellerware.org
> >
>

--14dae9399dc7fdd4aa04cba8ec37--