On 2007-11-8 10:32, Andrea Righi wrote: > > Since rysnc is generally supplied by the linux distribution separately, I > > would not like to see SI require something that will conflict with what > > is provided by the base system. That's a headache and will just leave a > > lot of users back at SI 3.9.x until their distro goes to rsync 3. For > > fedora (which we use), that means a new release (at least f8, maybe f9) > > as they would not put it into an existing release as an update (if I > > understand the policy, and the policy is why we use fedora). > > There's a misunderstanding here... using rsync 3.0.0pre4 wouldn't introduce > any additional requirements. It will be only used by systemimager itself to > build the initrd_template and the BOEL initrd.img (read: it'll be > automatically shipped into the systemimager initrd).
Ah, I get it. The rsync3 is packaged into the autoinstall system. Would getimage/updateclient continue to use the system rsync? Still, I can't really evaluate the stability risk in using rsync3 internally, but there don't appear to be complications for users aside from that. -- Patrick Dowler Tel/Tél: (250) 363-6914 | fax/télécopieur: (250) 363-0045 Canadian Astronomy Data Centre | Centre canadien de donnees astronomiques National Research Council Canada | Conseil national de recherches Canada Government of Canada | Gouvernement du Canada 5071 West Saanich Road | 5071, chemin West Saanich Victoria, BC | Victoria (C.-B.) ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
