Bugzilla – Bug 118730
documentation for drpmsync lacks vital information
Last modified: 2011-05-04 15:04:02 UTC
When dtrying to setup a drpmsync server I found that only full rpms get transmitted thus rendering the tool useless. Only after reading the source code I found that only the client is able to create useful deltas thus making an additional pre-staging server a requirement. In my opinion it is essential do document this in the man page section for the server. Additionally there are some options I found in the code not documented in the man page. BTW: Some more comments in the code might be helpful. ;-)
Hey, all this is work in progress... Regarding the prestage server, one could - write a small rsync client in perl (not very hard, I'll probably do this), and/or - use drpmsync to copy the rpms/create the deltas from a local source. Anyway, as I said, work in progress. drpmsync was mainly written to sync trees here at novell. We'll also use it to provide the newest OSS rpms. Patches/ideas welcome...
Ok, how about adding the following paragraph to the SERVER MODE section of the man page: Note that the current server implementation does not create non-trivial patch RPMs on demand. If you actually want to make use of the RPM specific features of drpmsync you should create two servers. The first server should not be open to the public but only to the machine where the second server is located. This server does not yet serve RPM deltas and thus the network bandwidth should not be a limiting factor between both server machines (which could actually be on one host). On the machine the second (public) server resides on you fetch the contents via drpmsync client from the first server with the option generate_deltas truned on. That way you would enable the second server to actually serve delta RPMs.
Thanks. Let's see what I can implement for the next version...
Sorry, no time to work on drpmsync.