FS#56128 - {mkinitcpio} patch for --rsyncable option
Attached to Project:
Arch Linux
Opened by Charles Duffy (charles-dyfis-net) - Thursday, 26 October 2017, 17:43 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 08 December 2019, 11:25 GMT
Opened by Charles Duffy (charles-dyfis-net) - Thursday, 26 October 2017, 17:43 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 08 December 2019, 11:25 GMT
|
Details
Presently, running consecutive cpio builds with the same
inputs, the resulting outputs can be almost entirely
different. This means that using a storage system such as
`rdiff-backup`, a binary-delta-based update distribution
mechanism such as `casync`, or the like will effectively
need to store both old and new builds in full, no matter how
small the actual change between them.
With the attached patch, consecutive builds which previously had ~27.5MB of deltas are reduced to only 120KB of data transmitted by rsync to sync them (at a cost of somewhat worse compression and lost timestamps within the cpio archive, hence keeping this option off-by-default). 
0001-Add-off-by-default-rsync...
(3.6 KiB)
|
This task depends upon
Closed by Dave Reisner (falconindy)
Sunday, 08 December 2019, 11:25 GMT
Reason for closing: Implemented
Additional comments about closing: But also sort of wontfix? went in a different direction to get to the same end result.
Sunday, 08 December 2019, 11:25 GMT
Reason for closing: Implemented
Additional comments about closing: But also sort of wontfix? went in a different direction to get to the same end result.
Kind of awkward to do patch review here, but...
Why does it matter whether rsyncable is used, for purposes of sorting the filelist passed on to cpio? AFAIK there is no downside to doing it either way... it simplifies the logic.
Will be starting an arch-projects thread momentarily. No position taken on whether to keep this ticket open in the interim. (BTW, might not hurt to mention the arch-projects list in the HACKING or README files going forward).