bundle depedencies?

[jdonaldson]

If someone could figure out how to do this properly, or at least settle on a metadata form for declaring bundle dependencies, they would win the internets.

VundleVim/Vundle.vim#7

[junegunn]

Yeah, that would be nice, though I don't have any burning desire to win the internet. Actually the lack of proper dependency control mechanism has been something that always irked me about Vim plugins. But even if I come up with some kind of dependency specification standard, it's painfully obvious that I don't have enough influence on the other plugin developers to enforce them to follow the rule. But still, it's a very intriguing subject. I'll think about that.

[junegunn]

I've added an experimental dependency resolution scheme.

See: https://github.com/junegunn/vim-plug#dependency-resolution

I don't expect to see a plugin with Plugfile anytime soon, but yeah, we'll see. 💩

[jdonaldson]

Nice! I think I'll switch for a while and see how it goes.

Do you have an rtp specification for bundles? Sometimes certain bundles have files in a weird directory. Some sort of additional object hash would also let you manually specify dependencies for bundles too:

Plug 'rstacruz/sparkup', {'rtp': 'vim/', 'dependencies': ['foo/bar', 'foo/etc'] }

[junegunn]

Ah, that rtp thing 😵
I agree that we need it. I'll look into it and let you know soon.

dependencies in your example, however I don't think it's really necessary. We can just write,

Plug 'rstacruz/sparkup', {'rtp': 'vim/'}
Plug 'foo/bar'
Plug 'foo/etc'

[junegunn]

It's done. Let me know if you have a problem with it.

[Shougo]

Can you support vim-pi and addon-info.json?

https://bitbucket.org/vimcommunity/vim-pi

I want to support vim-pi/addon-info.js in neobundle.

[jdonaldson]

Neato
On Mar 25, 2014 4:25 PM, "Shougo" notifications@github.com wrote:

Can you support vim-pi and addon-info.json?

https://bitbucket.org/vimcommunity/vim-pi

I want to support vim-pi/addon-info.js in neobundle.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-38633989
.

[junegunn]

@Shougo Maybe. Could you please open a new issue so that we can continue the discussion there?
I only have a rough idea of what addon-info.json does (or the problem it tries to solve). The above link doesn't seem to provide enough explanation on the matter.

[Shougo]

Thanks. But Mr.Bram thinks about plugin managers and plugin central managers.
I wait until Mr.Bram decides.

https://groups.google.com/forum/#!topic/vim_use/xtNFTzDEZ3Y

[junegunn]

@Shougo Sounds great. Honestly I wasn't so sure if addon-info.json was THE format we should all support.

[Shougo]

Because, most used plugin information format is addon-info.json.
Unfortunatelly, Plugfile and neobundle recipes format are not used.
This may be changed by Mr.Bram's decision.

[junegunn]

@Shougo I'm just saying that it has never reached critical mass to be realized as a de facto standard we should all settle for. For example, out of 38 plugins I currently use, only one has addon-info.json. I still think addon-info.json is better than the known alternatives in that it's more neutral and not bound too tight to a specific plugin manager implementation, but is it the best format we could conceive of? I don't know. The best option I think at this stage is that Bram finally comes up with a canonical format we all should follow.

[Shougo]

Because vim-pi uses the format and it supports more popular plugins, I think it is worth supporting.
But this may be changed by Mr.Bram's decision.