 |
 |
To date, we've not been able to actually use any of the clever ABI at the packaging level because there's no great way to export, from an Xrootd server build, the set of minimal plugin versions. All of this is encoded in C++ and packaging systems, of course, aren't C++ parsers! Could we have two tools: 1. Tool that prints in a simple, machine-parseable, line-delimited format, all the plugin APIs provided by the version of Xrootd the tool was packaged with. 2. Tool that scans a given shared module for known Xrootd versioning symbol names and prints out the corresponding build-time information from within the module. Given this, we could write RPM macros that automatically generate package dependency information, allowing us to detect incompatibilities at install time (and even have `yum` resolve these issues during upgrades). -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/926 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1