| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 <2009> 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 <2009> 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: why doesnt the include file install set the file permisions to unwritable? |
| From: | Andrew Johnson <[email protected]> |
| To: | [email protected], Jeff Hill <[email protected]> |
| Cc: | "'Core-Talk'" <[email protected]> |
| Date: | Thu, 19 Nov 2009 09:43:52 -0600 |
On Thursday 19 November 2009 08:12:45 Eric Norum wrote:
> All files in the<base>/ include directory on my OS X machine are mode
> 644, as they should be.
I think Jeff is really asking why they aren't installed 444, which is a good
question which Janet can't explain either (lost in the mists of pre-history,
or before CVS anyway). It should be easy to change the install mode; there
are three X_PERMISSIONS variables in configure/CONFIG_COMMON:
BIN_PERMISSIONS = 555
LIB_PERMISSIONS = 644
INSTALL_PERMISSIONS = 644
Changing the 644 to 444 would then make the installed files read-only. We
don't know why there is a different LIB_PERMISSIONS setting since I would
expect libraries to use the BIN_PERMISSIONS, but they don't. Janet agrees we
should fix this.
- Andrew
--
The best FOSS code is written to be read by other humans -- Harald Welte