Re: [CentOS] Shared object packaging in rpm

On 25/06/11 02:15, Joseph L. Casale wrote: I whipped up a quick spec to package Zenoss' wmi client and noticed it creates a libasync_wmi_lib.so.0 and libasync_wmi_lib.so.0.0.1 that their python script would otherwise copy during its install routine (obviously I wrote a native rpm section

Re: [CentOS] Shared object packaging in rpm

On 25/06/11 10:04, Ned Slider wrote: On 25/06/11 02:15, Joseph L. Casale wrote: I whipped up a quick spec to package Zenoss' wmi client and noticed it creates a libasync_wmi_lib.so.0 and libasync_wmi_lib.so.0.0.1 that their python script would otherwise copy during its install routine

Re: [CentOS] Shared object packaging in rpm

http://www.ibm.com/developerworks/library/l-shobj/ Thanks, that was informative. As Ljubomir said, libasync_wmi_lib.so.0 will be a symlink to libasync_wmi_lib.so.0.0.1. You can use objdump to find the soname(s) for shared objects, e.g: objdump -p /path/to/libasync_wmi_lib.so.0.0.1 | grep

[CentOS] Shared object packaging in rpm

I whipped up a quick spec to package Zenoss' wmi client and noticed it creates a libasync_wmi_lib.so.0 and libasync_wmi_lib.so.0.0.1 that their python script would otherwise copy during its install routine (obviously I wrote a native rpm section for installation). Anyone know the naming

Re: [CentOS] Shared object packaging in rpm

Joseph L. Casale wrote: I whipped up a quick spec to package Zenoss' wmi client and noticed it creates a libasync_wmi_lib.so.0 and libasync_wmi_lib.so.0.0.1 that their python script would otherwise copy during its install routine (obviously I wrote a native rpm section for installation).