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?
Regards,
Chip Campbell
--
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
