> On Feb 24, 2015, at 9:14 AM, Lukasz Janyst <[log in to unmask]> wrote:
>
> Hello Everyone,
>
> as you have probably noticed, I had recently merged the ceph stuff done by Sebastien, but it looks like we will not be able to build and distribute it against vanilla EPEL. The reason is that xrdceph requires the Giant release of CEPH (the most recent one) and the ceph version in EPEL is quite old.
Is it a build-time or a run-time dependency?
In other projects, it's been useful to turn build-time deps into a run-time one. This way, the module can build but only works if the appropriate library is on the host.
> Unless I have missed something we have three ways out of this situation:
>
> 1) We disable XrdCeph by default until Giant hits EPEL and let the interested parties rebuild on their own.
>
How about:
1.1) We additionally provide a xrootd-ceph spec file so interested parties have to do very minimal amount of work.
By making it a separate source RPM, it makes it easier for everything to live happily in a single repo.
> 2) We require everyone wanting to install xrootd (even without xrdceph) to also enable the CEPH proprietary repository. The reason why this would need to be done always is that the CEPH guys have a nasty habit of providing in their repo not only the CEPH packages but also some upgraded versions of basic system packages that we may (or may not) depend on. We have hit these dependency issues in EOS already.
Yeah - this sounds pretty horrible. Ceph is a huge amount of baggage for many use cases.
>
> 3) We provide two separate repos for two flavors of xrootd (with or without xrdceph).
>
This also sounds pretty high-maintenance.
Brian
########################################################################
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
|