Hi all,
I am packaging vim-unite [1] and vim-proc [2] (will submit review BZs some later time). vim-proc needs a shared object for its functionality and places it here: /usr/share/vim/vimfiles/autoload/vimproc_unix.so
Since /usr/share is generally for arch-independent data [3], I thought this was a no-no (rpmlint complains with arch-dependent-file-in-usr-share). I did notice that at least pitivi, coccinelle and rubygem-gherkin all ship such .so files under /usr/share so I wondered if this is tolerated when it makes sense (arch-independent plugins which also need a shared object) or should I see if there are different approaches ?
From a quick look on Debian as well, I could not find a single VIM
plugin that ships a .so file, so I'd need to see where I'd actually place it. Create /usr/lib64/vim/add-ons/vim-proc or something similar? This will probably need some coordination with the vim maintainers in such case.
Any thoughts on this?
cheers, Michele
[1] http://acksyn.org/files/rpms/vim-unite/ [2] http://acksyn.org/files/rpms/vim-proc/ [3] http://www.linuxbase.org/betaspecs/fhs/fhs.html#usrshareArchitectureindepend...
packaging@lists.fedoraproject.org