I am packaging vim-unite  and vim-proc  (will submit
review BZs some later time). vim-proc needs a shared object
for its functionality and places it here:
Since /usr/share is generally for arch-independent data ,
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
Any thoughts on this?
Michele Baldessari <michele(a)acksyn.org>
C2A5 9DA3 9961 4FFB E01B D0BC DDD4 DCCB 7515 5C6D