From: Andreas Schwab <schwab@linux-m68k.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: umask and permissions of installed files
Date: Thu, 03 Sep 2009 09:44:11 +0200 [thread overview]
Message-ID: <m33a74bhh0.fsf@hase.home> (raw)
In-Reply-To: <jwv1vmoycjv.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 02 Sep 2009 22:42:34 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> In connection with addressing bug#3800 I would like to ask: what is
>> the right thing to do wrt the installing user's umask when installing?
>
>> The two reasonable options would seem to be
>
>> i) ignore it, and make the install world-readable, with the exception
>> that pre-existing "common" directories should not have their
>> permissions altered, as requested in bug#3800. Ideally, the install
>> whould warn about any non-standard permissions.
>
>> ii) respect it, and don't mess with the permissions of the install at all
>
>> Option i) seems like the right thing to me.
>
>> At the moment, there is an inconsistent mish-mash of i) and ii).
>
> What's the "standard procedure"?
The "standard procedure" is to use install which ignores umask.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2009-09-03 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 1:07 umask and permissions of installed files Glenn Morris
2009-09-03 2:42 ` Stefan Monnier
2009-09-03 3:16 ` Glenn Morris
2009-09-03 7:44 ` Andreas Schwab [this message]
2009-09-03 7:54 ` Miles Bader
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m33a74bhh0.fsf@hase.home \
--to=schwab@linux-m68k.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).