Re: [p4] Null directory (//) not allowed

Posted on behalf of forum user 'Sambwise'.

The "+" symbols in your View indicate an "overlay mapping",
aka (speaking as one who has helped many people untangle these things) "a
one-way ticket on the pain train".  Don't say nobody warned
you!  The big gotchas to watch out for:

1) When files in any of those directories have the same name, the higher
precedence (last in the mapping) wins, even if it's a deleted file.
2) When you add a new file, higher precedence wins unless you specify a lower
precedence depot file for the add operation.  I forget how good P4V is
at handling this (it used to not do it at all but I think that got fixed with
some sort of popup dialog that asks you to pick an option, in which case I guess
you'll be getting prompted on every single file you add,
yuck).  From the command line you can do it by providing a fully
qualified depot path to "p4 add".
3) It will not be obvious when looking at your local tree how everything maps
back to the depot, so if any of this stuff gets mixed up, it could easily go
undetected for a while and then cause an inexplicable failure down the
line.  Consider this carefully when setting up testing and build
processes.

As a separate thing, I recommend replacing that  *.*  with just  *  unless you
are very deliberately trying to exclude files that don't have a  .  in their
name. Double wildcards are a performance time bomb and should be avoided if
there's no real need for them.



--
Please click here to see the post in its original format:
  http://forums.perforce.com/index.php?/topic/5477-null-directory-not-allowed
_______________________________________________
perforce-user mailing list  -  [email protected]
http://maillist.perforce.com/mailman/listinfo/perforce-user