Date: Tue, 6 Jul 2004 23:52:55 -0700 From: "David O'Brien" <obrien@freebsd.org> To: Kirk Strauser <kirk@strauser.com> Cc: freebsd-current@freebsd.org Subject: Re: Rewrite cvsup & portupgrade in C Message-ID: <20040707065255.GB38356@dragon.nuxi.com> In-Reply-To: <200407062323.02854.kirk@strauser.com> References: <E1Bhd1M-000KEo-Nz@smp500.sitetronics.com> <20040707031735.GA3540@frontfree.net> <20040707041220.GA35497@troutmask.apl.washington.edu> <200407062323.02854.kirk@strauser.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 06, 2004 at 11:22:58PM -0500, Kirk Strauser wrote: > Not as long as you're on a system that supports it. For example, OpenBSD > doesn't have an m3 port for non-x86 platforms (at least not the last time I > checked). Although that doesn't directly relate to FreeBSD, it's does mean > that cvsup probably isn't as widespread as it would be if it had a nice, > portable C implementation. I'm sorry, but I don't have a lot of sympathy for this situation. It would not take someone more than a weekend to get OpenBSD Alpha and sparc64 support since these work just fine on FreeBSD. Since 'ezm3' will soon be GCC 3.2.3 based, PowerPC support for *BSD should not be hard. The only major platform that will be an issue is AMD64. I hope to be able to pull off targeting AMD64 with the next release of 'ezm3'; but there were some significant AMD64 bugs in GCC 3.2.3... > Would there be any way to get most of cvsup's functionality out of rsync? It > wouldn't hurt my feelings if cvsup were replaced by rsync for the common > cases (4-STABLE, 5-CURRENT, etc.). Sure -- that's CVSup's "check out" mode; which Csup does. So that gives two "rsync-like" choices in 'C'. :-) -- -- David (obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040707065255.GB38356>