VOMS Packaging notes

Note on how the voms released has changed for EMI:

  1. All the *_"globus_flavor" versions of the APIs have disappeared.
  2. The libvomsc.so library has disappeared. It was deprecated since 2006, and since 2006 libvomsapi offered both the C and C++ interfaces. Link to that instead.
  3. Globus is no longer a dependency, neither at buildtime nor at runtime. Since the library only used OpenSSL, and the Globus we got from VDT uses the system OpenSSL anyway, there was no reason to continue depending on Globus. This has some consequences on the usage of libvomsapi in a threaded environment, see the section about thread in release notes of this patch ( patch 2717) for details
  4. Those same notes also mention that as a consequence, the RetrieveFromCtx() function/method is no longer available. It was not a widely used function anyway, and example code on how to obtain the same functionality may be seen in the org.glite.security.voms-compatibility CVS module. That module has not been ported to EMI yet, and it would be preferable that people simply grab that code. If needed it can be ported to EMI.
  5. As a consequence of all the previous points, the new libraries are incompatible at the ABI level with the ones in EGEE, and consequently have had their version increased to one. (Known bug: They do not. This will be fixed monday (15.11.2010) morning)

As a consequence - org.glite.security.voms-api-c was replaced/included in/by org.glite.security.voms-api-cpp

Correspondence among conf.name, contents, and rpm in EPEL

ETICS module content RPM in EPEL
org.glite.security.voms-api-cpp C,C++ APIs voms
org.glite.security.voms-api includes,links voms-devel
org.glite.security.voms-server vomsd voms-server
org.glite.security.voms-clients clients voms-clients
org.glite.security.voms-api-java Java APIs vomsjapi
EMI.voms.javadoc Javadocs vomsjapi-javadoc

Furthermore, a voms.pc is installed which can be used to determine where the libs are. Use it as normal with pkgconfig.

VOMS EMI 2 packaging

The VOMS core and libraries ETICS components naming changes in EMI 2 in the following way:

ETICS module pre-EMI2 ETICS module content Package name
emi.voms.voms-api org.glite.security.voms-api-cpp C,C++ APIs voms
emi.voms.voms-api-devel org.glite.security.voms-api development package for C/C++ apis voms-devel
emi.voms.voms-api-java org.glite.security.voms-api-java Java APIs voms-api-java
emi.voms.voms-clients org.glite.security.voms-clients clients voms-clients
emi.voms.voms-server org.glite.security.voms-server server voms-server

If you have dependencies on one of the above components specified in your ETICS configurations please update them following the table above.

Changes in VOMS Java APIs

In EMI 2 the package name for VOMS Java APIs changes from vomsjapi to voms-api-java. The ETICS build for this module produces two rpms, one for the library and one for the javadoc.

The VOMS jar library is now staged in

/usr/share/java/voms-api-java.jar. 

A symbolic link for the old jar name (vomsjapi.jar) is also in place for backward compatibility. The link will be removed in EMI3.

-- AndreaCeccanti - 19-Dec-2011

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2011-12-19 - AndreaCeccantiExCern
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback