Martin,
I gather from your letter to Christopher that rsync provides more reliable access to the updated package descriptions than CVS. Are there any other advantages to making the switch to rsync?
It may be considered an advantage or not, but selfupdate-rsync lets you keep and update only the package tree that you have activated in your fink.conf file. In /sw/fink, you don't get "10.2" and "10.2-gcc3.3" and "10.3" anymore with subdirectories "stable" and "unstable" in each, but only (for example) "10.3/stable". It is thus faster and less disk-consuming, but you don't have access to the file discriptions in the unstable tree if you don't activate it.
A disadvantage is that you don't have access to a file's history as you have with cvs. But this makes rsync also less failure-prone than cvs, because it just overwrites your local files with the ones on the server, it does not try to merge possible local modifications into the global history of a file.
The main reason for the introduction of the rsync update method was the unreliability of sourceforge's anonymous cvs access this summer which did not work sometimes for whole weeks and still has problems as we have seen (works fine at this moment, though). The rsync access is on a different server system independent of sourceforge that is working very well right now. The master repository is still on sourceforge, though, and makes heavy use of sourceforge's infrastructure, as are these mailing lists.
-- Martin
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Fink-beginners mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-beginners
