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...
On 11/23/2014 03:51 AM, Michele Baldessari wrote:
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...
They definitely belong in %{_libdir}/vim/.... But yeah, looks like this will require some coordination.
And yeah, looks like some cleanup needs to be done:
# repoquery --whatprovides /usr/share/*.so --source | sort -u coccinelle-1.0.0-0.rc20.1.fc21.2.src.rpm condor-8.1.4-7.a1a7df5.fc21.src.rpm elixir-1.0.2-1.fc21.src.rpm ircd-ratbox-2.2.9-3.fc21.src.rpm koffice-kivio-1.6.3-43.fc21.src.rpm netbeans-platform-7.0.1-11.fc21.src.rpm pitivi-0.93-7.fc21.src.rpm pitivi-0.94-3.fc21.src.rpm rawstudio-2.0-16.fc21.src.rpm rosa-launcher-2.0.0-5.fc21.src.rpm R-statmod-1.4.20-2.fc21.src.rpm rubygem-gherkin-2.12.2-2.fc21.src.rpm smb4k-1.1.2-3.fc21.src.rpm spring-96.0-6.fc21.src.rpm spring-98.0-2.fc21.src.rpm thermostat-1.0.4-4.3.fc21.src.rpm
Can we get rpmlint run as part of taskotron?
Can we get rpmlint run as part of taskotron?
It is... it's just still a bit difficult to search for the results: https://taskotron.fedoraproject.org/resultsdb/results?testcase_name=rpmlint
packaging@lists.fedoraproject.org