I see @amadio issue here that this change would remove some extra steps in the release process. On the other hand, if we don't automatically build Ceph because we don't know what to build against then a site would have to build the complete xrootd package to just get the Ceph part built (unless we provide an option to only build the Ceph part). As for making it difficult in the future not exactly so. For your first update after including Ceph in the repo you will need to generate a patch file and apply it to a clone of the xrootd repo (it should be clean as you are the only one modifying the code) and the create a pull request. After that, your changes would be made in the cloned xrootd repo and that step is pretty straightforward. @amadio could you comment on whether this is all correct?

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/pull/2008#issuecomment-1550398177", "url": "https://github.com/xrootd/xrootd/pull/2008#issuecomment-1550398177", "name": "View Pull Request" }, "description": "View this Pull Request on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

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