Add official support for VAM #4

Closed
ZyX-I opened this Issue Jun 13, 2013 · 3 comments

Comments

Projects
None yet
2 participants
@ZyX-I

ZyX-I commented Jun 13, 2013

If one uses VAM and you have a simple structure in the addon-info.json in plugin root in each of the dependent repositories then one does not have to know about the dependency as it gets installed and activated automatically:

{
    "dependencies": {
        "vim-misc": {}
    }
}

(name "vim-misc" should be equal to the name of the plugin on www.vim.org).

It is an issue for each of the dependent plugins, not to vim-misc itself, but it is simpler to post it here.

@xolox

This comment has been minimized.

Show comment Hide comment
@xolox

xolox Jun 13, 2013

Owner

I've never used VAM (although I'd heard of it before). So all I have to do is to add the file with the name addon-info.json to the root of the repository of each plug-in, with the literal contents you gave, and it will work?

Owner

xolox commented Jun 13, 2013

I've never used VAM (although I'd heard of it before). So all I have to do is to add the file with the name addon-info.json to the root of the repository of each plug-in, with the literal contents you gave, and it will work?

@ZyX-I

This comment has been minimized.

Show comment Hide comment
@ZyX-I

ZyX-I Jun 13, 2013

Yes. It should even work without this because I added necessary information to VAM-known-repositories, but after I add something there I do not check whether everything is still applicable. So official support from the author (you) is better: I most likely won't notice change in requirements of the plugins I do not use if you e.g. split vim-misc further like I was not noticing this dependency appear for a few weeks: VAM-kr contains too much plugins.

Existing addon-info.json file overrides data from VAM-kr.

ZyX-I commented Jun 13, 2013

Yes. It should even work without this because I added necessary information to VAM-known-repositories, but after I add something there I do not check whether everything is still applicable. So official support from the author (you) is better: I most likely won't notice change in requirements of the plugins I do not use if you e.g. split vim-misc further like I was not noticing this dependency appear for a few weeks: VAM-kr contains too much plugins.

Existing addon-info.json file overrides data from VAM-kr.

xolox added a commit to xolox/vim-tools that referenced this issue Jun 22, 2013

@xolox

This comment has been minimized.

Show comment Hide comment
@xolox

xolox Jun 22, 2013

Owner

I use a Python script to manage the development of my Vim plug-ins and I just changed that script to automatically generate and commit addon-info.json when I do releases. So as I release changes to all of my Vim plug-ins, they will gain support for VAM. Thanks for the suggestion!

Owner

xolox commented Jun 22, 2013

I use a Python script to manage the development of my Vim plug-ins and I just changed that script to automatically generate and commit addon-info.json when I do releases. So as I release changes to all of my Vim plug-ins, they will gain support for VAM. Thanks for the suggestion!

@xolox xolox closed this Jun 22, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment