vim-addons respects umask a bit too much. It creates anything in
/var/lib/vim, aka for any user, respecting the umask of the calling
process, 027 in my case. So no user can read the stuff.

| drwxr-x--- 4 root root 4096 Jul  7 14:50 /var/lib/vim/addons/
| drwxr-x--- 2 root root 4096 Jul  7 14:50 /var/lib/vim/addons/ftdetect/
| lrwxrwxrwx 1 root root   41 Jul  7 14:50 /var/lib/vim/addons/ftdetect/puppet.vim -> /usr/share/vim/addons/ftdetect/puppet.vim
| drwxr-x--- 2 root root 4096 Jul  7 14:50 /var/lib/vim/addons/syntax/
| lrwxrwxrwx 1 root root   39 Jul  7 14:50 /var/lib/vim/addons/syntax/puppet.vim -> /usr/share/vim/addons/syntax/puppet.vim

Bastian

Attached patch uses a specific mode when installing an addon as root.

However, this doesn't correctly handle the case of an actual root user
installing addons for themself.  This would be better handled by
tracking whether it's a "system" install or not, instead of an install
being performed by root.

James McCoy escreveu isso aí:

Right. I can't think ATM of a way to get that information ("is this a
system-wide install?") available in a sane way down to the addon level
without a major refactoring of the code ... :-/

Control: clone -1 -2
Control: severity -2 normal
Control: retitle -2 Honor root's umask when performing root-user (not system) actions

Ok, I'm creating a separate issue to track detecting that difference and
I'll push my proposed fix for the original issue shortly.

Cheers,