[SCM] vim-addon-manager packaging branch, master, updated. v0.4.4-52-geef7258

Antonio Terceiro terceiro at debian.org
Tue Jan 31 23:33:47 UTC 2012


The following commit has been merged in the master branch:
commit 4fa7d3b67a52bfbb17bbd4dfe611e118c532a942
Author: Antonio Terceiro <terceiro at debian.org>
Date:   Mon Jan 23 21:05:23 2012 -0200

    Sorting the TODO list; priority = top to bottom

diff --git a/TODO b/TODO
index 41311af..222fbd9 100644
--- a/TODO
+++ b/TODO
@@ -1,11 +1,9 @@
-- Allow the admin to declare whether they want registered addons to be
-  automatically installed system-wide.  Use debconf & dpkg triggers?
+Short term
+==========
 
 - find a good name (debvam, debundle, ?) for the directory where the new style
   addons are installed.  Using the same as pathogen is not a good idea.
 
-- update vim-policy http://pkg-vim.alioth.debian.org/vim-policy.html/
-
 - implement a way of modifying the runtimepath to include the directories under
   ~/.vim/bundle. Maybe bundling vim-pathogen together with this package.
 
@@ -14,6 +12,7 @@
   runtime bundle/vim-pathogen/autoload/pathogen.vim
   call pathogen#infect()
 
+- update vim-policy http://pkg-vim.alioth.debian.org/vim-policy.html/
 
 - figure out the upgrade path for addons that move from the "everything mixed
   together in /usr/share/vim/addons" to the "new layout", i.e. all addon files
@@ -21,7 +20,22 @@
   /usr/share/vim/addons/$whatever/$addonname
 
   - add a `cleanup` command to remove dangling symlinks from the target
-    directory.
+    directory?
+
+  - add an `upgrade` command to figure out which addons should be installed
+    based on the dangling symlinks, them removing those symlinks and
+    re-installing the addons in the new way?
+
+    - addons could just change the 'files' attribute to 'oldfiles' or something
+      like that, so that they could reconstruct objects using the legacy addon
+      class, them remove the legacy installations, then installing the new
+      addon.
+
+Middle/Long term
+================
+
+- Allow the admin to declare whether they want registered addons to be
+  automatically installed system-wide.  Use debconf & dpkg triggers?
 
 - implement some way to install stuff from remote servers:
   - git repositories

-- 
vim-addon-manager packaging



More information about the pkg-vim-maintainers mailing list