[m-rev.] for review: install mercury with umask 022
Mark Brown
mark at csse.unimelb.edu.au
Tue Sep 19 14:20:47 AEST 2006
On 18-Sep-2006, Julien Fischer <juliensf at csse.unimelb.edu.au> wrote:
> On Mon, 18 Sep 2006, Mark Brown wrote:
> >It appears to be very easy to accidentally install things over the existing
> >standard library, in part because we install things in such a way that they
> >are writeable by group mercury. Is there any reason we need the installed
> >files to be group writeable?
>
> One reason is that it's less of a hassle for us to modify things if
> installations become broken in some way that requires a bit of manual
> intervention.
Presumably this doesn't happen often enough to worry about needing to
`sudo -u mercury' or whatever.
> Also, for those working on the deep profiler it's often necessary to
> replace the installed mdprof_cgi script.
The test_mercury script doesn't create /usr/lib/cgi-bin, so that directory
will remain group writeable if it already is so.
I'll go ahead and commit that change.
Cheers,
Mark.
--------------------------------------------------------------------------
mercury-reviews mailing list
Post messages to: mercury-reviews at csse.unimelb.edu.au
Administrative Queries: owner-mercury-reviews at csse.unimelb.edu.au
Subscriptions: mercury-reviews-request at csse.unimelb.edu.au
--------------------------------------------------------------------------
More information about the reviews
mailing list