FreeLists / openbeos / [openbeos] Re: Organizational question

["Mikael Jansson (mailing lists)" <lists@xxxxxxxxxxxxxxxxx>]

Waldemar Kornewald <Waldemar.Kornewald@xxxxxx>:
>
> >>2) All of the developers who are working with the Haiku code know 
> > > how 
> >>to use
> >>CVS. Not everyone knows how to use Perforce. It may be very easy to 
> >>use, but
> >>people will still have to learn it. In addition, the migration from 
> >>CVS to
> >>Perforce will interrupt development.
> > 
> > 
> > It shouldn't. At least not more than that every dev has to learn 
> > about 
> > how to use p4 which is pretty easy and straight forward.
> 
> I started reading the docs some days ago and I must say it is a very 
> complex product if you want to set-up your own server. This 
> configuration files model reminds me of Linux and it does not feel 
> BeOS-like. It is powerful, but do we need that?
> 
Are you serious?

http://www.perforce.com/perforce/demo/unix.html

Setting up a new Perforce repository for me takes 5 minutes, adding 5 
users takes 10 minutes.


>
> I think after you finished with the complicated one-time "p4 client" 
> process (there are many settings which are not obvious if you did not 
> read the manual) you have a powerful and (from then on) easy to use 
> tool.
> If we write a small newsletter article that describes how to set up 
> the 
> client view and how to sync, submit, and make changes no problems 
> should 
> occur.
>
If nobody else wants to write that introduction (axeld?), I could do 
it, but it'd have to wait two weeks.  You learn the basics really 
quick.

Also, setting up the client spec is just a matter of changing the 
client name, and possibly the client workspace root.  Then you store 
all variables in a file .p4env in the top-level, and after that all P4 
ops will automagically use those settings. (Need to set P4CONFIG=.p4env 
in UserSetupEnvironment first, though.)

It's really transparent.  I use three different clients, and switching 
between them is just to change directory. 


--
Mikael Jansson
http://mikael.jansson.be