rootfs folders have 775 permissons

[hphilm]

@ShadowApex during my work on AerynOS/recipes#1532 I found out that rootfs has 775 folder permissions for folders like lib and share. On AerynOS it created some issues after I updated to uutils-coreutils 0.7.0. There folders with 755 are hidden for our package manager. Other folder permissions get recorded. So why is 775 used in rootfs?

Here some more details:

root@boulder:~/v0.76.0.tar.gz
# umask
0022

Source folders have permissions as:

root@boulder:~/v0.76.0.tar.gz
# ls -lasih rootfs/usr
total 0
67657413 0 drwxrwxr-x 1 root root 16 Apr  1 01:02 ./
67657412 0 drwxrwxr-x 1 root root  6 Apr  1 01:02 ../
67657414 0 drwxrwxr-x 1 root root 22 Apr  1 01:02 lib/
67657427 0 drwxrwxr-x 1 root root 52 Apr  1 01:02 share/

And the target adopts them as it should:

root@boulder:/mason/install
# ls -lasih usr
total 0
67685784 0 drwxr-xr-x 1 root root 22 Apr  7 07:10 ./
67685783 0 drwxr-xr-x 1 root root  6 Apr  7 07:10 ../
67685785 0 drwxr-xr-x 1 root root 24 Apr  7 07:10 bin/
67685787 0 drwxrwxr-x 1 root root 22 Apr  7 07:10 lib/
67685800 0 drwxrwxr-x 1 root root 52 Apr  7 07:10 share/

So I have to call find rootfs -type d -exec chmod 755 {} \; to update the folder permissions in setup process.

[pastaq]

They have those permissions in the repo so that we can work with them for development. The makefile then installs them with correct permissions for other build systems. If you need something specific for the AerynOS build system it would probably be best to make a PR to add a build target into the makefile, or change your recipe in some way so that it sets the permissions per folder when installing instead of relying on recursive searches. I'm not really interested in working around broken permissions in the main repo constantly to fix a problem that should be resolved in the packaging step.

[hphilm]

All good. No worries regarding the source folder permissions. I already added a permission change in the package recipe. I just found out when I used uutils-coreutils 0.7.0. Before cp -A created 755. Will look into install targets more ...