Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Andreas Radke píše v Po 18. 07. 2011 v 18:26 +0200:
For a long time now we see lots of files installed with permission 444
and 555 in ArchLinux. We are not sure if this is caused by a bug in our
chroot environment using fakeroot or due to the LibO installer. Because of
the missing write permission our build tools fail to strip the symbols.
So we apply this:

 #fix http://bugs.archlinux.org/task/17656
 find ${pkgdir} -perm 444 -exec ls -lh {} \;
 find ${pkgdir} -perm 444 -exec chmod 644 {} \;
 find ${pkgdir} -perm 555 -exec ls -lh {} \;
 find ${pkgdir} -perm 555 -exec chmod 755 {} \;

I was always curious about the too strict permissions. I havn't seen it
in other software.

The attached patch should change it. I am not sure if it is acceptable
for others, though.


Best Regards,
Petr

PS: If you want to test it, please, remove scp2/unxlng* and
rebuild/deliver it. Just for sure ;-)
--- scp2/inc/macros.inc.old     2011-05-18 17:51:47.000000000 +0200
+++ scp2/inc/macros.inc 2011-07-18 19:58:27.000000000 +0200
@@ -92,10 +92,10 @@
 #endif
 
 #define BIN_FILE_BODY \
-        UnixRights   = 555
+        UnixRights   = 755
 
 #define TXT_FILE_BODY \
-        UnixRights   = 444
+        UnixRights   = 644
 
 #define USER_FILE_BODY \
         UnixRights   = 644

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.