[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#445866: ITP: perforce -- closed source revision control system

On Mon, 2007-10-08 at 14:42 -0700, Tyler MacDonald wrote:
> Florian Weimer <fw@deneb.enyo.de> wrote:
> > Seems to me that this depends on Perforce.  D'oh.
> > 
> > (I don't know anything about Perforce.  Perhaps it's really dangerous
> > software.  But perhaps it's just non-free.)
> 	Perforce is an absolutely *excellent* VCS with the unfortunate
> distinction of being proprietary. SubVersion can do most (but not all) of
> what it does, albeit 10 times slower. Still, I've migrated all of my stuff
> over to subversion, because, well, subversion is free. Perforce is free (as
> in "free beer") for open source developers, if you want more than 2 users on
> one VCS server, you have to sign a contract, get a license, give the
> perforce people full access to your repo, sign a new contract whenever you
> server's IP address changes, and renew each year....

Slightly off topic, but you don't need to give the perforce people
access to you repo (unless you really want them to come in a fix
something) and you don't need to renew each year (unless you want
support from them).

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: