From owner-freebsd-hackers Sat Sep 8 21:29:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smile.idiom.com (inreach-gw1.idiom.com [209.209.13.26]) by hub.freebsd.org (Postfix) with ESMTP id 7DC7137B408 for ; Sat, 8 Sep 2001 21:29:45 -0700 (PDT) Received: from mdaxke (adsl-63-196-0-143.dsl.snfc21.pacbell.net [63.196.0.143]) by smile.idiom.com (8.9.1/8.8.5) with SMTP id VAA43455 for ; Sat, 8 Sep 2001 21:29:39 -0700 (PDT) Message-ID: <0ab401c138e7$f0ff2b60$6501a8c0@mdaxke> From: "Mark D. Anderson" To: Subject: Re: local changes to CVS tree Date: Sat, 8 Sep 2001 21:28:27 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Terry Lambert " wrote: > Any chance of getting CVSup to transfer from a remote repository > to a local vendor branch, instead of from a remote repository to > a local repository? > > This would be incredibly useful for building a combined local > source tree from multiple project's CVS repositories. It could > be used by FreeBSD for a number of "contrib" things, as well... this has probably been discussed before, but has the freebsd project considered using perforce for the central repository? perforce runs on freebsd. the company gives free licenses to free software projects, though it is not itself a source-available product. that may bother the religiously open-source, though it really is far superior to CVS. perl5 development has been using perforce; i don't know if they've decided yet what perl6 will use (and in fact that may depend on what sourceforge will supply them). see for example this post on why the perl project is using it: http://www.mail-archive.com/bootstrap@perl.org/msg00589.html as compared to cvs, it has support for views (including both multiple repositories and server-side proxying to other repositories), advanced branching/merging, atomic change sets, and is fast. there are various ways to offer at least readonly cvs access even if committers adopted perforce, as outlined in the link above. (in addition to various master-master and master-slave relationships between perforce and cvs, it should also be possible to have a pserver proxy server fronting over perforce. that would probably be ideal, though i don't think a trustworthy implementation of that yet exists.) -mda To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message