Re: Packages

On Mon, Mar 07, 2016, Nikolay Aleksandrovich Pavlov wrote:
> Without isolated namespaces this is absolutely useless behaviour. If A
> depends on B, C depends on B and D does not depend on anything and
> plugin manager created packages (A,B1), (C,B2) and (D) then out of B1
> and B2 there will be only one used, whatever was found first (or last
> or first with errors from last, depending on how plugins and plugin
> manager are written). On the other hand creating package (A,B,C) and
> (D) if B is a library, A and D are filetype plugins and C is a
> universal linter would be rather strange choice, also where plugin
> manager is going to pull a package name from? Not to mention what is
> needed to be done if a plugin E is added that depends on D and B?
> Moving plugins around without an explicit reason is not fine.
>
> So if plugin manager is using packages it will create one package
> containing all plugins. Maybe additionally a user-defined packages
> that are needed to group plugins loaded at request by user when it is
> needed to load at one request more then one plugin, without "grouping
> by dependencies" nonsense.

I think it would be nice -- but plugins and VimL would have to be
heavily modified -- if things worked much like npm packages. I.e. each
plugin could have a tree of dependencies inside it, and it would only
recognize the particular versions bundled inside. Likewise, other
plugins outside its tree would not see its bundled plugins.

--
Eric Christopherson

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.