From Fedora Project Wiki
(initial guidelines for CMPI Plugins)
 
m (fix typo)
Line 2: Line 2:




# Make sure each provider Requires: tog-pegasus (or sblim-sfcb). Each provider should "Require" either cim sever for now. This is going to change in future, to Requires: cim-server
# Make sure each provider Requires: tog-pegasus (or sblim-sfcb). Each provider should "Require" either cim server for now. This is going to change in future, to Requires: cim-server
# All plugins are shared libraries, ending in .so.  These are to be installed in the /usr/%{_libdir}/cmpi/ directory.
# All plugins are shared libraries, ending in .so.  These are to be installed in the /usr/%{_libdir}/cmpi/ directory.
# Each provider should register in %postin and unregister in %preun to the cim server.
# Each provider should register in %postin and unregister in %preun to the cim server.
# Some of the providers may have hard-coded shared object names, which are dlopen()ed at runtime.  rpmlint will throw warnings to move *.so files to a -devel package, but this would be incorrect for these packages.  Such warnings may be ignored.
# Some of the providers may have hard-coded shared object names, which are dlopen()ed at runtime.  rpmlint will throw warnings to move *.so files to a -devel package, but this would be incorrect for these packages.  Such warnings may be ignored.
# All the registration and mof files go to /usr/share/%{name}
# All the registration and mof files go to /usr/share/%{name}

Revision as of 17:22, 25 January 2010

These are guidelines for packaging CMPI plugins, used by the tog-pegasus or sblim-sfcb CIMOMs. Such plugins are called "CIM providers", and each uses the CMPI interface to the CIMOM.


  1. Make sure each provider Requires: tog-pegasus (or sblim-sfcb). Each provider should "Require" either cim server for now. This is going to change in future, to Requires: cim-server
  2. All plugins are shared libraries, ending in .so. These are to be installed in the /usr/%{_libdir}/cmpi/ directory.
  3. Each provider should register in %postin and unregister in %preun to the cim server.
  4. Some of the providers may have hard-coded shared object names, which are dlopen()ed at runtime. rpmlint will throw warnings to move *.so files to a -devel package, but this would be incorrect for these packages. Such warnings may be ignored.
  5. All the registration and mof files go to /usr/share/%{name}