 |
 |
On Fri, 22 May 2015 08:28:13 +0200 Jan Iven <[log in to unmask]> wrote: > On 05/21/2015 10:43 PM, Lukasz Janyst wrote: > > It is needed, but it is needed only once. There is not and should > > not be any explicit dependency on the compat package anywhere, only > > implicit soname dopendencies. Therefore, the exact name or version > > of the compat package is completely immaterial. As long as there is > > a package in the yum's universe that has appropriate implicit > > provide tags for the wanted sonames, yum will know what to do. > > > > In the long run these compat packages should come from a separate > > SRPM and be on their own release cycle, ie. no cycle at all, since > > they contain the code that does not change anymore. In the short > > term, just use the one from 4.1.x, the one from 4.2.x would have > > been identical modulo the version. > > Background on our side is unpackaged ROOT versions on AFS/CVMFS that > need libXrdClient.so.1 (and which are heavily used by the > experiments). > > We have explicitly added xrootd-client-compat to our package sets. > Having "any other" RPM provide these libraries would be OK for us, we > will just make sure that package is present. All this should work fine, except that Elvin has found a bug that will need to be fixed in a package with a superseding version number. Cheers, Lukasz ######################################################################## 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