Date: Sun, 14 Nov 2010 12:13:38 +0100 From: "Simon L. B. Nielsen" <simon@nitro.dk> To: Patrick Bihan-Faou <patrick.bihan-faou@teambox.fr> Cc: freebsd-hubs@freebsd.org, freebsd-questions@freebsd.org, Ken Smith <kensmith@buffalo.edu> Subject: Re: Sorry state of the rsync based CVS,replication Message-ID: <EAD59A4B-8F27-4173-BD5D-5B9E58560B4F@nitro.dk> In-Reply-To: <4CDCFF30.60307@teambox.fr> References: <4CC81EE7.4020607@teambox.fr> <1289492183.40288.37.camel@bauer.cse.buffalo.edu> <4CDCFF30.60307@teambox.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12 Nov 2010, at 09:47, Patrick Bihan-Faou wrote: > Don't take this as flamebait, because I have no intention in starting = a war on this particular issue, but as good as cvsup is, this is = unfortunately a fairly isolated tool that, from my prospective (which is = necessarily biaised and incomplete), does not offer any feature = compelling enough to prefer it over rsync in our case. That position is = by essence just a personal view, applicable to me only and not to = anybody else. Also I have to admit that now that the m3 dependency is = gone with csup, it becomes easier to return to it. The issue is not to remove CVS via rsync - just to remove it from the = FTP collection where it doesn't belong. There is nothing which prevents mirror sites from providing access to = the CVS repo via rsync, even if they get it via CVSup... If it's useful (IE, any of the primary mirrors requests it) we can = probably rather easily set up rsync access via cvsup-master. That said, = I think rsync access is likely not too interesting for most master = mirrors as they likely provide access to the repo via CVSup already, so = they have cvsup installed already. --=20 Simon L. B. Nielsen Hat: FreeBSD.org clusteradm
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EAD59A4B-8F27-4173-BD5D-5B9E58560B4F>