XRootD software framework

Edit Package xrootd

XRootD software framework is a fully generic suite for fast, low latency and scalable data access, which can serve natively any kind of data, organized as a hierarchical filesystem-like namespace, based on the concept of directory. As a general rule, particular emphasis has been put in the quality of the core software parts.

Refresh
Refresh
Source Files
Filename Size Changed
_multibuild 0000000055 55 Bytes
harden_cmsd@.service.patch 0000000851 851 Bytes
harden_frm_purged@.service.patch 0000000887 887 Bytes
harden_frm_xfrd@.service.patch 0000000875 875 Bytes
harden_xrootd@.service.patch 0000000863 863 Bytes
xrootd-5.7.0.tar.gz 0006807467 6.49 MB
xrootd-find-gtest.patch 0000000396 396 Bytes
xrootd-rpmlintrc 0000000264 264 Bytes
xrootd-user.conf 0000000138 138 Bytes
xrootd.changes 0000043674 42.7 KB
xrootd.spec 0000020188 19.7 KB
Revision 87 (latest revision is 88)
Atri Bhattacharya's avatar Atri Bhattacharya (badshah400) accepted request 1186244 from Atri Bhattacharya's avatar Atri Bhattacharya (badshah400) (revision 87)
* Update to version 5.7.0.
* Add xrootd-find-gtest.patch: Add `find_package` snippet to CMakeLists.txt to avoid linking issues when building tests (we do not, but still this fixes the cmake config for when we might).
* Add new BuildRequires to build additional libraries and plugins:
Comments 2

Stefan Brüns's avatar

Just a small heads up, regarding generating/packaging the Python bindings:

https://github.com/amadio/xrootd/commit/39585c3274b8569cd98a8239e3db18db728ea1ce

This should allow to build the bindings in a separate package, or maybe a multibuild. This also allows to reduce the number of rebuilds, as e.g. any changes in the non-default python version will no longer cause any rebuilds of the main package.


Atri Bhattacharya's avatar

Many thanks Stefan, will add that commit to the version 5.5.5 update I am in the process of packaging and see how it goes.

openSUSE Build Service is sponsored by