On 04/24/2016 04:41 PM, Willy Sudiarto Raharjo wrote:
I don't understand what you mean;) When I wrote -current, I meant Slackware -current. Should the -L switch be there or not in SlackBuilds.org? :)Also, there is a difference between the permissions in SlackBuilds.org and Slackware's -current: SlackBuilds.org: find -L . \ \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ -o -perm 511 \) -exec chmod 755 {} \; -o \ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; Slackware's -current: find . \ \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \ -exec chmod 755 {} \; -o \ \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \ -exec chmod 644 {} \; 750 and 640 are not present in Slackware's SlackBuilds.we expect that maintainers stick to the template, so we should use -L
why not using this
find . \
-type d \
-exec chmod -c 755 {} \; -o \
\( -type f ! -perm /a+x \) \
-exec chmod -c 644 {} \; -o \
\( -type f -perm /a+x \) \
-exec chmod -c 755 {} \;
Best regards,
Marko Vujkovic
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
