> - VAM supports a pool of known packages. Thus if a package is obviously > replaced/outdated/unmaintained there is a way to tell the users. > Thus this reduces questions about "why doesn't my old sander's > snipmate fail with X" on irc.
>- VAM allows package maintainers to specify dependencies in a package > description, thus installing it by name is enough, no need to declare > dependencies in vimrc. Yes. I think VAM has great repository information. But neobundle has similar feature. It is recipe. You can read sample recipes in the following repository. https://github.com/Shougo/neobundle-vim-recipes >The real question is: How can NeoBundle and VAM collaborate? Even if >some parts are implemented differently, dosen't it make sense to >collaborate on "installation instructions" etc ? Yes. I get the request. https://github.com/Shougo/neobundle.vim/issues/117 Your repositories are great. But I think to support current VAM-known repositories in neobundle is hard work. I must write converter. I have not much time for it. In Vim todo list, Vim needs standard plugin management. >- Improve plugin handling: Automatic updates, handle dependencies? > E.g. Vundle: https://github.com/gmarik/vundle I think Vim needs standard plugin repositories than standard plugin management system. Users may use different plugin management system instead of standard. But all plugin management system needs plugin repositories information. >- it allows arbitrary sources, git(hub),svn, etc. neobundle has supports of git, svn, hg. Bazzaar and archives are not. You can add the features easily. -- -- 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/groups/opt_out.
