Re: Packages

On 5 March 2016, Bram Moolenaar <Bram@moolenaar.net> wrote:
>
> Ben Fritz wrote:
[...]
> > You talked about dependencies...with this method, won't you
> > potentially have multiple copies of every dependency, if every
> > plugin that has a dependency defines a package instead to bundle the
> > plugin with all its dependencies?
>
> I would expect people who create several plugins that depend on a
> common library to have one package with all these plugins.
>
> If a plugin depends on something made by another, you can clone that
> and add it to your package. The advantage is that you can test that
> specific version. Might have a name conflict if the user downloads
> it separately, thus you may want to rename it. And of course keep it
> updated.
[...]

So what happens when two packages come with conflicting versions of
the same library? It seems to me the result is a much bigger potential
for trouble than before, when the user explicitly had to manage versions
of libraries and the like. At the very least it makes things harder to
debug. Testing plugin X version x against library Y version y would be
nice of course, but I don't think it can work without proper namespace
separation. Simply renaming files and directories won't be enough.

Tangentially related again: since these latest versions have been
pathogen slayers (like it or not, people are thinking about them that
way :)), pathogen has one more useful feature, the :Helptags command.
It runs :helptags in the directories in runtimepath. Perhaps add a
:packhelptags[!] that does the same thing for packages (with the bang
version forcing update of help for disabled plugins)?

/lcd

--
--
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.