DOORS/LOS178 Build Procedure
- Managed to install DOORS. Turns out that using Tomcat for FlexLM requires port 19360 not port 19353
- Exported the HybridOS Build Procedure document to create the LOS178 2.1.0 Build Procedure document
- Attempting to document exactly what CVS access is given for a username in the readers/writers files depending on whether or not either file exists for the CVSAdm web app
Determining CVS Read/Write Access
CVS decides read/write access based on the presence of the user name in the files readers and writers in the repository. Additionally either or both of these files may be missing.
The CVS Manual says:
If readers exists, and this user is listed in it, then the user gets read-only access. Or if writers exists, and this user is not listed in it, then they also get read-only access (this is true even if readers exists but they are not listed there). Otherwise, she gets full read-write access.
Of course there is a conflict if the user is listed in both files. This is resolved in the more conservative way, it being better to protect the repository too much than too little: such a user gets read-only access.
Based on that the following describe the access granted to a user.
| Case | Readers | Writers | Read Access | Write Access |
|---|---|---|---|---|
| 1 | No File | No File | No | No |
| 2 | No File | Not Present | Yes | No |
| 3 | No File | Present | Yes | Yes |
| 4 | Not Present | No File | No | No |
| 5 | Not Present | Not Present | Yes | No |
| 6 | Not Present | Present | Yes | Yes |
| 7 | Present | No File | Yes | No |
| 8 | Present | Not Present | Yes | No |
| 9 | Present | Present | Yes | No |
- A strict intepretation of the CVS manual might lead you to believe that since readers does not exist and writers does not exist then it would fall into the "Otherwise" statement at the end of the first paragraph. However an argument can be made that the user is also not listed in the writers file because the writers file is not present. But I believe that no access should be granted.
- Readers does not exist and the user is not listed in writers so read only access.
- Readers does not exist but the user is listed in writers. So the user has write access. Does this imply read access? Does write-only access exist?
- User is not listed in the readers file and there is no writers file. This case is not covered by the CVS manual. My assumption is therefore no access. Again a strict interpretation might argue the "Otherwise" clause but I think not.
- User is not listed in the readers file nor in the writers file therefore read only access.
- User is not listed in the readers file but is listed in the writers file. User gets read/write access.
- User is listed in the readers file but there is no writers file. Read only access.
- User is listed in the readers file but not present in writers file. Read only access.
- User is listed in the readers file and the writers file. This is the conflict. Resolve the conflict by only providing read access.