#Source Controll Blues
20-Jul-93 09:38:33
Sb: #7080-#Source Controll Blues
Fm: Kevin Irlen 76666,2005
To: John Funk 70441,1047
<<<
When I called tech support, I was told this part of the manual was incorrect.
The command interface to source server isn't part of the product.
>>>
Sorry, but whoever you spoke to was misinformed! The command line interface is
definitely part of the product!
<<<
… the manual is that it doesn't describe what function the "SET PROJECTOR
DB.." menu provides. It brings up a dialog that asks what projector database
to select, but why are you selecting it , and what effect does this have on
anything else?
>>>
True, this could be documented better (at all); it does serve a function
though. You could in fact be switching between different projector db's.
<<<
…the manual says to use the MERGE BRANCH procedures to bring a version back
into the original tree. I discovered that the Menu interface doesn't provide
this feature at all. You can't get a branch of a tree back into the root with
what is included in Symantec C++.
>>>
Yes, unfortunately the manual mistakenly documents a feature of SourceServer
which is NOT available in Symantec C++. Merge Branch is an MPW script and can
only be used via the MPW editor.
<<<
I also discovered that the menu interface doesn't allow you to delete a
revision.
>>>
Not so, you do this with Undo CheckOut.
<<<
Another feature that isn't supported is checking in a file that isn't part of
the project. We have some documentation files that I would like to check in.
It seems the only way is to add it to the project with a .c or a .h extension.
>>>
Consider this suggestion noted.
<<<
… the only way to get all of the .h files to check in is to go into the
extensions area of the Think Project Manager options, and tell it to process .h
files with one of the compilers…
>>>
This is a known bug. A better workaround is to use the command line interface
to check the files in manually (CheckIn -new fullpathnameofyourfile).
<<<
…the release notes say to keep your projector databases to less than 50 files
or you will suffer "performance degradation". … So I thought it would make
sense to organize each of these folders into separate projector databases.
Because of the problems I had encountered with the manual so far I decided to
call Symantec tech support to get their views on organizing the project in
source server. Their response was that splitting the project between several
projector databases would cause problems and that it was best to use only 1
database.
>>>
Again, this is not the case, and my apologies for your having been misinformed.
You may certainly use multiple projector databases.
<<<
I checked in each sub-folder of files at separately. I still received timeout
errors, but my files did get checked in.
>>>
This timeout problem is being looked into.
<<<
After repeating the bus error several times narrowed the problem down to the
"Default directories" pull down. It doesn't seem to work when multiple folders
are involved.
>>>
Also being looked into.
<<<
I suggest when an apple event to source server times out, the user should be
prompted to continue waiting rather than simply aborting the process.
>>>
Suggestion noted.
<<<
After checking everything in I discovered that you can't "Name Revisions"
across multiple projector databases. Source server returns "NameRevisions –
File 'XXXXX' is not part of the project" for every files in one of the
databases.
>>>
This is true. This is not a feature of SourceServer.
<<<
For now I am now waiting for suggestions from our local apple rep, our local
Symantec rep, or anyone else.
>>>
[continued in the reply]