Three octal digits are not enough, we must also respect the
sticky/setuid/setgid bits. Even if these are mostly implied to be 0, we
should be explicit here. This should also help to prevent permission
clashes when more than one packages install the same directory.

Signed-off-by: Roland Hieber <[email protected]>
---
 * v2: unchanged

 doc/ref_make_macros.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/ref_make_macros.rst b/doc/ref_make_macros.rst
index 6f056adf3e7d..ae65cb9408cf 100644
--- a/doc/ref_make_macros.rst
+++ b/doc/ref_make_macros.rst
@@ -173,7 +173,7 @@ Some of the parameters have fixed meanings:
 **<GID>**
   Group ID the file should use in the target's root filesystem
 **<permission>**
-  Permission (in an octal value) the file should use in the target's root 
filesystem
+  Permission (as a four-digit octal value) the file should use in the target's 
root filesystem
 
 The remaining parameters vary with the use case:
 
@@ -384,7 +384,7 @@ The base parameters and their meanings:
 **<GID>**
   Group ID the file should use in the target's root filesystem
 **<permission>**
-  Permission (in an octal value) the file should use in the target's root 
filesystem
+  Permission (as a four-digit octal value) the file should use in the target's 
root filesystem
 
 The parameter <destination> is meant as an absolute path
 and filename in target's root filesystem. PTXdist searches for the source
@@ -581,7 +581,7 @@ The parameters and their meanings:
 **<GID>**
   Group ID the directories and files should use in the target's root filesystem
 **<permission>**
-  Permission (as an octal value) the library should use in the target's root
+  Permission (as a four-digit octal value) the library should use in the 
target's root
   filesystem (mostly 0644)
 **<libname>**
   Basename of the library without any extension and path
-- 
2.28.0


_______________________________________________
ptxdist mailing list
[email protected]
To unsubscribe, send a mail with subject "unsubscribe" to 
[email protected]

Reply via email to