Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 16 Mar 2003 16:32:48 -0700
From:      Nate Williams <nate@yogotech.com>
To:        "Jan Mikkelsen" <janm@transactionware.com>
Cc:        "'Nate Williams'" <nate@yogotech.com>, "'Terry Lambert'" <tlambert2@mindspring.com>, "'Sean Chittenden'" <sean@chittenden.org>, "'Sergey Babkin'" <babkin@bellatlantic.net>, <hackers@FreeBSD.ORG>
Subject:   RE: making CVS more convenient
Message-ID:  <15989.2464.921797.617183@emerger.yogotech.com>
In-Reply-To: <003301c2ec13$5c8614e0$fc5807ca@mosm1>
References:  <15989.1782.166458.477601@emerger.yogotech.com> <003301c2ec13$5c8614e0$fc5807ca@mosm1>

next in thread | previous in thread | raw e-mail | index | archive | help
> > The other solution to the problem is the P4 route.  Making things so
> > darn effecient that there's little need to have a local mirror.  Where
> > this falls down is when the remote developer doesn't have a 24x7
> > connection to the main repository.  From what I've been told ClearCase
> > allows for 'mirrored read-only' repositories similar to what 
> > most of the
> > open-source CVS developers have been doing with sup/CVSup for years,
> > although it's nowhere near as effecient as CVSup at creating 
> > snapshots.
> 
> The current version of Perforce has "p4proxy" which caches a local copy
> of the depot files used.

Does it still require a working net link to the master repository?  When
it was originally released, I remember it being useful for slow links,
but not so good on non-existant links (ie; airplane rides, etc..)

> What is the status of Perforce in the FreeBSD project?  Is the issue the
> absence of a "p4up"?  Licensing?  Inertia?

See the archives for a more thorough discussion, but I believe the
licensing is the biggest issue.  If we moved to use commercial software,
it would make our development much more difficult for the average
developer to track our progress.



Nate

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15989.2464.921797.617183>