Debian-specific packaging (was [Vimoutliner] biking with a notebook)

[Ross Boylan]

On Wed, 2008-07-30 at 07:13 -0800, Mark S. wrote:
> As near as I can tell, VIM changed the path placements for plugins (at 
> least in debian) but the Vimoutliner package did not change with it. So 
> the required files get dropped some place that VIM doesn't recognize. 
> After installing the package, I had to work to figure out which files 
> needed to be moved, and where.
> 
> This probably is also why the ,, doesn't work either. I added a 
> directive to my vimrc file and now it works, but I really shouldn't have 
> to do that since the documentation is written referring to ",," and no 
> where does it say "Oh yeah, use \\ if ,, doesn't work".
> 
> I mentioned before that I was concerned whether VO was still being 
> maintained (since the web site is in lock down mode and there are 
> several unfinished sub-tasks). This is the kind of thing I mean. A lot 
> of people use debian/ubuntu these days and most will want to use the 
> package system to load VO -- especially since that is the recommended 
> way to do things these days. Anyone attempting to do so may come away 
> with the impression that VO is DOA.
> 
> -- Mark

>From /usr/share/doc/vim/NEWS.Debian.gz on lenny:
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 <zack at debian.org>  Thu, 19 Jul 2007 23:28:44
+0200


Unfortunately, this is a recurring source of trouble for those coming to
it new.  I can see the reasons for doing it, and I can see it's a
problem that you install a package and it doesn't "just work."

The \\ apparently is the vim standard way of doing things, and so it was
left as that rather than ,,.  Probably Debian should change the docs,
though it is mentioned in point 3
of /usr/share/doc/vim-vimoutliner/README.Debian:

3) Upstream documentation (located in
   /usr/share/doc/vim-vimoutliner/README) mentions ,, as the
   prefix to most VO commands. In reality, even the upstream
   package actually uses the native Vim <localleader> variable,
   which is set to \ (backslash) by default, so that a command
   listed in the README file as ,,B -- "Make body text start with
   a space", is actually executed when you type \B (with default
   defintion of <localleader>).
   
   If you want to use different localleader uncomment in
   /etc/vim/vimoutlinerrc the following line and change the value
   of the variable to whatever you want.

       "let maplocalleader = ",,"	" this is prepended to VO key

> 
> --- On Tue, 7/29/08, Scott Scriven <vimoutliner at toykeeper.net> wrote:
> 
>  > From: Scott Scriven <vimoutliner at toykeeper.net>
>  > An upgrade broke it one day, and I haven't seen it work
>  > since...  
>  > even with a completely fresh install on a blank system.
>  > But I
>  > don't really have to care now that it's checked
>  > into my $HOME
>  > repository.  I "svn co" once on each fresh host,
>  > and everything
>  > just works.
>  >
> 
> _______________________________________________
> VimOutliner mailing list
> VimOutliner at vimoutliner.org
> http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner