- changed status to resolved
Some authors of one-file plugins are not creating repository with correct directory tree
You can find these plugins by searching for scm.*archive
in plugin/vim-addon-manager-known-repositories.vim
file. Currently they are added with code like
let s:scm_plugin_sources['StarRange'] = {'url': 'https://bitbucket.org/shu/starrange/raw/default/starrange.vim', 'archive_name': 'starrange.vim', 'type': 'archive', 'script-type': 'utility', 'title': 'StarRange'}
This issue is to discuss what should be done with them (first is the most prefered):
- Add postinstall and postupdate hooks and create normal directory structure with them.
- Use raw file url (like above).
- Ignore them.
- Add code that is able to checkout into
plugin_root_dir/subdirectory
.
First is prefered because these hooks will also be used to run additional commands if required (for example, Command-T
installation and update does require running ruby extconf.rb && make
) and also deal with other violations (like putting doc and plugin into the root directory) which can’t be dealt with fourth solution. Second just looks like a hack and makes plugin unconditionally updated. Third is bad because it makes VAM support less plugins which can’t be good from my point of view. Fourth is a hack too, but it is to be added to another place.
Comments (2)
-
reporter -
reporter Current state: is and will be using 2, 1 will be written at request.
- Log in to comment