Hello Piotr,
I didn't understand, could you please elaborate about this procedure as mentioned in the last update. It would be really helpful if you share any useful link/doc to understand what you actually meant. Yea correct, normally we do this procedure but it takes more time. But here my intention is to how to find out the rpm which caused the change. I think we are in opposite direction.
>> But wouldn't be faster and/or more convenient if you would just recompile binaries in-place (or use network symlinks)
Thanks
On Thu, Mar 23, 2017 at 6:47 PM, Piotr Dałek <piotr.dalek@xxxxxxxxxxxx> wrote:
On 03/23/2017 02:02 PM, nokia ceph wrote:
Hello Piotr,
We do customizing ceph code for our testing purpose. It's a part of our R&D :)
Recompiling source code will create 38 rpm's out of these I need to find
which one is the correct rpm which I made change in the source code. That's
what I'm try to figure out.
Yes, I understand that. But wouldn't be faster and/or more convenient if you would just recompile binaries in-place (or use network symlinks) instead of packaging entire Ceph and (re)installing its packages each time you do the change? Generating RPMs takes a while.
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
