From owner-freebsd-current@FreeBSD.ORG Wed Jul 7 06:52:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA55416A4CE for ; Wed, 7 Jul 2004 06:52:56 +0000 (GMT) Received: from TRANG.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8377743D6B for ; Wed, 7 Jul 2004 06:52:56 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by TRANG.nuxi.com (8.12.11/8.12.11) with ESMTP id i676quei012906; Tue, 6 Jul 2004 23:52:56 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.11/8.12.11/Submit) id i676qtOI012904; Tue, 6 Jul 2004 23:52:55 -0700 (PDT) (envelope-from obrien) Date: Tue, 6 Jul 2004 23:52:55 -0700 From: "David O'Brien" To: Kirk Strauser Message-ID: <20040707065255.GB38356@dragon.nuxi.com> References: <20040707031735.GA3540@frontfree.net> <20040707041220.GA35497@troutmask.apl.washington.edu> <200407062323.02854.kirk@strauser.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200407062323.02854.kirk@strauser.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-current@freebsd.org Subject: Re: Rewrite cvsup & portupgrade in C X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2004 06:52:57 -0000 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)