diff options
| author | Boud Roukema <boud@cosmo.torun.pl> | 2020-04-23 02:36:43 +0200 |
|---|---|---|
| committer | Boud Roukema <boud@cosmo.torun.pl> | 2020-04-23 02:36:43 +0200 |
| commit | 52e9ae4463684584fd8bd7a4655b7b181471cfbe (patch) | |
| tree | 1968d3f36857487f1ec1e50f4c50bc4be2f06852 /paper.tex | |
| parent | e1adce48eaaf1f83ed442ba07093f2f28ee5ecd9 (diff) | |
4.5 Project analysis - multi-user
Increase by 5 words. We don't need to give a big warning here,
but "Permissions management" is meant to be a brief way of saying
that whether or not different users can really read/write/execute
in subdirectories will firstly depend on whether the user who
cloned Maneage has handled these permissions correctly and whether
s/he is able to allow others to edit in his/her subdirectories.
Comment: Users would have to check who else is logged in at the time,
who else is running jobs, and so on. On a supercomputer this might
make sense, to avoid unnecessary recompiles. Anyway, this edit
summary is not the place to discuss this...
Diffstat (limited to 'paper.tex')
| -rw-r--r-- | paper.tex | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -662,11 +662,11 @@ Modern version control systems provide many more capabilities that can be levera \subsection{Multi-user collaboration on single build directory} \label{sec:collaborating} -Because the project's source and build directories are separate, it is possible for different users to share a build directory, while working on their own separate project branches during a collaboration. -Similar to the parallel branch that is later merged in Figure \ref{fig:branching}(a). -To enable this mode, \inlinecode{./project} script has a special \inlinecode{--group} option which takes the name of a (POSIX) user group in the host OS. +Because the project's source and build directories are separate, an option is provided for different users to share a build directory, while working on their own separate project branches during a collaboration. +This is similar to the parallel branch that is later merged in Figure \ref{fig:branching}(a). +To enable this mode, the \inlinecode{./project} script has an option \inlinecode{--group} that must be given the name of a (POSIX) user group in the host OS. All files built in the build directory are then automatically assigned to this user group, with read and write permissions. -Of course, avoiding conflicts in the build directory, while members are working on different branches is up to the team. +Permission management and avoiding conflicts in the build directory while members work on different branches is the responsibility of the team. \subsection{Publishing the project} \label{sec:publishing} |