Having built and tested 3.0.7 and ready to send it out into production, can anybody point me to 'best practices' for updating the binary and man pages and other issues around upgrading from the dodgy v2.6.9 that ships with late-10.4-thru-10.7?
Is anybody making substantial effort to check versions and conflicting options by writing a wrapper and linking the new version from /usr/local/bin, or just overwriting the old one and adding it to a list of checks for testing new server builds and OS upgrades? Not having replaced an OSX tool in the past, I've got no idea if Apple is prone to update these utils, or just 'fix' what I've done automatically during routine checks and system upgrades. Any experiences would be appreciated. Regards, Bryan -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
