cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michal Mocny <mmo...@chromium.org>
Subject Re: Non-Git Plugin Dependencies
Date Wed, 04 Sep 2013 01:54:05 GMT
Sounds reasonable to me.

Conceptually, I'm not sure why the syntax for (2) shouldn't do what you
request when the url for the original plugin was a local path?  Maybe just
a bug?

-Michal


On Tue, Sep 3, 2013 at 9:38 PM, Jeffrey Heifetz <jheifetz@blackberry.com>wrote:

> We were working on a redistribution of Cordova that included some plugins
> and ran into a use-case not covered by the current plugin spec.[1]
>
> Currently there are two ways to specify a dependency
> 1. Using a combination of url, commit and subdir which plugman will use to
> clone down a repo and install
> 2. Set the url to ".", skip the commit and specify a subdir relative to
> the root of the repo. Plugman then runs git-rev parse to find the root and
> install from there.
>
> I would like to propose a third way which would be relative to the current
> install and not use git at all
> 3. Skip the url, skip the commit and specify a subdir relative to the
> current plugin.xml.
>
> This would allow us to distribute a version of cordova with plugins to
> anyone without an unnecessary requirement on git (considering the plugins
> are fully installed)
>
>
>
> 1. http://cordova.apache.org/docs/en/3.0.0/plugin_ref_spec.md.html
>
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-public
> information. Any use of this information by anyone other than the intended
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be unlawful.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message