[6202] in SIPB bug reports
Re: sipb-nonmem and prospectives with write bits on install volumes in sipb locker
daemon@ATHENA.MIT.EDU (Jacob Morzinski)
Wed Oct 30 14:31:52 1996
To: Sam Hartman <hartmans@MIT.EDU>
Cc: Salvatore Valente <svalente@MIT.EDU>, bug-sipb@MIT.EDU, jmorzins@MIT.EDU
In-Reply-To: Your message of "28 Oct 1996 18:29:36 -0500."
<tsl918qacrj.fsf@tertius.mit.edu>
Date: Wed, 30 Oct 1996 14:31:12 EST
From: "Jacob Morzinski" <jmorzins@MIT.EDU>
On Mon, 28 Oct 1996, Sam Hartman <hartmans@MIT.EDU> wrote:
> I would much prefer if you had given him write access to the
>source and build volumes, then installed stuff when he said it was
>ready. I don't think this is much extra work, and gives you a good
>chance to look at the quality of the release engineering and
>maintainability of his builds.
Actually, I don't even have access to the build volumes. The group
(currently named) sipb-nonmem has 'rlidwk' access to the
sipb-new/src directory, and to the sipb-new/arch/* directories, and
_no_ subdirectories of those. Since build, lib, and bin were
created before the acl change, they are closed to sipb-nonmem.
(Well, there are two directories under 'src' that sipb-nonmem can
make changes in, because I created those myself, after the acl of
the parent had been changed.)
I don't particularly need to have access to the arch/* directories,
but it would be nice to be able to use the build directories
underneath them. Would it make people happier if sipb-nonmem were
removed from the access list for sipb-new/arch/*, and added to the
access list for sipb-new/arch/*/build ?
--
Jacob Morzinski jmorzins@mit.edu
