Hi Lukasz,
If the decision is that server depends on client as well, then my question is invalid, and "libs" seems to be fine as well. the only other question I have is the xrdadler32 binary should be in client because it is also a client tool (to check xrdadler32 at the remote xrootd server), and its man page is already in client rpm.
regards,
Wei Yang | [log in to unmask] | 650-926-3338(O)
On May 12, 2011, at 2:28 AM, Lukasz Janyst wrote:
> Hi Wei,
>
> I don't really understand the question... the server depends on the
> client, so if you type "yum install xrootd-server" the client will be
> installed as well. I agree that xrootd-libs may be somewhat
> superfluous, but it is supposed to contain the utility libraries
> (neither client nor server related).
>
> Cheers,
> Lukasz
>
> 2011/5/11 Yang, Wei <[log in to unmask]>:
>> Hi Lukasz,
>>
>> Tools like xrdcp, xrd, xrdadler32 will likely be used by both client and server, for example, the FRM stage-in script on the server side will likely need them. It likes like you already have a xrootd-libs that hold common stuffs, except its name is "libs". How will we handle this?
>>
>> regards,
>> Wei Yang | [log in to unmask] | 650-926-3338(O)
>>
>>
>> On May 11, 2011, at 9:29 AM, Lukasz Janyst wrote:
>>
>>> Dear all,
>>>
>>> I have made a rc1 tag and built the RPMs which you can access here:
>>> http://xrootd.cern.ch/sw/releases/3.0.4-rc1/
>>>
>>> Cheers,
>>> Lukasz
>>
>>
|