Charles Campbell wrote:
> Bram Moolenaar wrote:
> > I'm thinking of a kind of manifest that specifies these dependencies.
> > When we standardize that it's still possible to use a choice of plugin
> > managers.
> FWIW, GLVS (getscript) supports plugin dependencies. A number of my
> plugins have lines such as
>
> " GetLatestVimScripts: 1066 1 cecutil.vim
>
> in scripts other than cecutil which tell getscript that the current
> script also depends upon cecutil.vim. So is it better for the plugin
> writer to explicitly state such dependencies as getscript promotes, or
> is it better to have a centralized manifest with them. How will that
> manifest be maintained, updated, etc?
Since many plugins consist of several files, and we would like to check
the dependencies before downloading all the files, the best place for
these dependencies is to have them in a separate manifest file.
Another advantage is that there would be one central place where plugin
authors upload the newest manifest file. For the moment assume that's
the script storage in vim.org. This also solves the problem of scripts
on vim.org being one file.
The manifest can specify any place, including git repo's, where to fetch
the files.
One could also fetch a manifest from elsewhere (e.g. by simply editing
it) and then run the plugin installer/updater. The dependencies can be
in the form of just a plugin ID, to be found in the central repository,
but it could also be the URL of that dependency's manifest file. That
way a plugin author can also publish alpha and beta versions, with
yet unreleased dependencies, before making the fully tested plugin
available at vim.org.
Using URLs for the location is flexible and easy to debug. Using single
files avoids problems with unpacking archives, the need to first install
tools, etc. I believe all respositories support downloading individual
files. What this does NOT support is further developing the plugin or
merging local changes. Normal users won't need that.
--
An easy way to determine if you have enough teamwork to be doomed is simply to
measure how long it takes from the time you decide to go to lunch together
until the time you actually eat.
(Scott Adams - The Dilbert principle)
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
