Does anyone have experience with perforce and rails/capistrano?  Just
looking for any tips/tricks you may have for dealing with it all.

I am used to working with subversion, but there are some little gotchas with
perforce that are driving me nuts.  Namely, when the app is under perforce
control everything local is read only.   Migrations fail because schema.rb
is read only.  I can Œopen¹ it for editing and run/edit the app for a
while...but as soon as I submit to perforce, everything changes back to read
only.  Pain in the arse.  I could keep schema.rb out of version control, but
I want it in there.  Also, if I want to add a new directory of files to the
depot, I can¹t run p4 add ./... Because the command shell doesn¹t expand
P4¹s ³...² wildcard.  I have to use >find . -type f ­print | p4 ­x- add ­f.
I miss subversion¹s ³svn add .²  Renaming a file is worse.  p4 integrate
old_filename new_filename, p4 delete old_filename, p4 submit.  Lastly, in
textmate, there is the Control+Shift+4 to bring up the perforce menu, where
I can select ³open file for editing,² but I¹m used to simply clicking on a
file, edit something real quick, save & close.  Then later simply committing
to subversion, knowing that things are ok.  Having to bring up that perforce
menu for every single file I edit is going to be a drag.  Tell me it¹s all a
nightmare and I¹ll be waking up soon.

Any tips or capistrano recipes for working with perforce would be greatly
appreciated.

-=Randy


--~--~---------~--~----~------------~-------~--~----~
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
-~----------~----~----~----~------~----~------~--~---

Reply via email to