Issue 735274: FILEMODE not honoured (original) (raw)

Issue735274

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification

Title:	FILEMODE not honoured
Type:	Stage:
Components:	Build	Versions:

process

Status:	closed	Resolution:	wont fix
Dependencies:		Superseder:
Assigned To:	jackjansen	Nosy List:	jackjansen, loewis
Priority:	normal	Keywords:

Created on 2003-05-09 15:07 by jackjansen, last changed 2022-04-10 16:08 by admin. This issue is now closed.

Messages (3)
msg15940 - (view)	Author: Jack Jansen (jackjansen) *	Date: 2003-05-09 15:07
The Python build process doesn't honour the FILEMODE setting in Makefile.pre.in (or passed in at install time with "make FILEMODE=664 install") because configure sets the install command to an explicit "${INSTALL} -m 644" in stead of to "${INSTALL} -m ${FILEMODE}". DIRMODE and EXEMODE are handled correctly. Please let me know whether you agree and assign back to me, if you agree I'll put the changes in.
msg15941 - (view)	Author: Martin v. Löwis (loewis) *	Date: 2003-05-11 20:40
Logged In: YES user_id=21627 I'm probably missing something: Where precisely is EXEMODE being used? As for FILEMODE: Is it important that this is honored? Users wanting to override this can also override INSTALL_DATA instead.
msg15942 - (view)	Author: Jack Jansen (jackjansen) *	Date: 2003-05-23 14:41
Logged In: YES user_id=45365 Hmm. It turns out that our configure.in isn't responsible for what gets set in the INSTALL_DATA and related variables: this is done by autoconf through the AC_PROG_INSTALL macro. I guess this means that fixing it is difficult, so let's forget about it. I'll continue doing the "chmod -R g+w" over the tree as I do now.