T
Thomas Mercer-Hursh
Guest
What you describe sounds like logical collapsing of the propath into a single directory. I.e., read and copy everything from the first directory, then read and copy everything from the second directory with no overwrite, etc. E.g., I used to set up my systems with a run directory for r code, a src directory for standard release source code, and cus directory for customer specific source code with a propath of run, cus, src. That way, it normally grabbed the .r, but if there was no .r then it would get the customer specific source, if any (quite rare in practice), and then look for standard release source code. Within each, there were top level directories for each module like AR and AP and within each of those package directories. If what you describe were done to this organization, one would have a perfectly sensible unified copy with the .r and the .ps in the same directories and cus source replacing any equivalent standard release source. Perfectly sensible, if that is the way it works. I think your problem is the propath structure. My default expectation would be that you would end up with three copies of everything, one in the root, one in AppServer, and one in AppServer/xx, but maybe it is clever enough to get rid of the duplicates and just keeps the first one.
Continue reading...
Continue reading...