The following NEWS item probably explains the problem; I don't know much
about vim. It's not clear to me if this policy means that vim addon
packages are not supposed to enable themselves (which seems perverse),
or just that they need to run a new tool to enable themselves.
Ross
vim (1:7.1-022+1) unstable; urgency=low
* /usr/share/vim/addons/ is no longer in the vim runtimepath
This is intended to avoid arbitrarly clashes among addons installed
system-wide and enabled by default, and to set up a common ground
for Vim
extensions of various kinds. From now on vim addons won't be
enabled by
default upon installation but will need to be enabled on a per-addon
basis
either in a system-wide manner (affecting all users of the system)
or by
each user who wants to use them. A tool exists for helping with
addon
management: it is called "vim-addons" and is shipped by the package
"vim-addon-manager"; all vim addon packages should recommend it.
For more information see the VIM packaging policy (available on the
web at
http://pkg-vim.alioth.debian.org/vim-policy.html/index.html) and the
manual page of vim-addons, available in the vim-addon-manager
package.
-- Stefano Zacchiroli <[EMAIL PROTECTED]> Thu, 19 Jul 2007 23:28:44
+0200
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
