for coding projects i prefer git. ( okay the first checkout takes a while but after that .... )
Tony Sergi schrieb: > Perforce actually is a lot better, but because I don't wanna pay for it, I > wouldn't use it for my personal team projects. > It's also got a much higher learning curve. > > So tbh, svn is best for small projects, p4 is wayyyyy better for huge ones, > especially ones with multiple sub projects. > > > > -Tony > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Garry Newman > Sent: June-26-09 12:38 AM > To: Discussion of Half-Life Programming > Subject: Re: [hlcoders] Sharing a depot in perforce > > Slightly off topic, but why do people use Perforce over SVN (besides 'cuz > Valve does')? > garry > > On Thu, Jun 25, 2009 at 4:25 PM, botman <[email protected]> wrote: > > >> Ben Tucker wrote: >> >>> im having some perforce troubles.... I have two computers on the >>> same >>> >> network, and both have perforce installed. I also have them sharing a >> netfolder ( a hard drive shared on the network ). I cant install >> perforce server on the netfolder because it isnt actually a server. Id >> like to store a perforce depot on there that both the computers can access >> and use. >> >>> I have attempted this by defining a depot on both of the comps. I >>> did >>> >> this with MSDOS: >> >>> p4 depot lido >>> and then changed the map: field to the netfolder's path and where I >>> had >>> >> the depot folder. This half worked, as they both could put files up >> there and do things with them. however, they could not detect the >> other computers files, so they could not collaborate. >> >>> anyone know how to fix this so they can collaborate on the same files? >>> >>> >> You shouldn't be "sharing" files anywhere. You install Perforce on >> one machine and run it as the server... >> >> >> http://www.perforce.com/perforce/doc.082/manuals/p4sag/01_install.html >> #1049719 >> >> You install Perforce on the other machine (the client) and run it as a >> client. >> >> The server creates a depot using "p4 depot SomeDepotName"... >> >> >> http://www.perforce.com/perforce/doc.082/manuals/p4sag/03_superuser.ht >> ml#1044923 >> >> ...and the client(s) access those files by creating a ClientSpec (or >> Workspace) that contains that depot. >> >> The client can then add new files to the depot or sync to revisions of >> files in the depot. The P4 server keeps track of which version of >> each file a client has. At no point should you "share" a file between >> the server and client by putting on a shared network resource where >> either machine can modify that file. >> >> -- >> Jeffrey "botman" Broome >> >> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlcoders >> >> >> > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlcoders > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlcoders > > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
