Khem Raj <[email protected]> writes: > alternatively you can exclude patches directory from feeding into > chmod
I do not think that excluding a single, implementation specific directory is a good idea. When this or a future package contains symlinks to outside the buildroot, problem would be triggered again. Doing blindly 'find | xargs chmod' is just wrong... I will submit a new patch which executes 'chmod -R u=rwx .' (this does not dereference symlinks) instead of using the find pipe. >> - find ./ -print|xargs chmod u=rwX >> + find ./ ! -type l -print|xargs chmod u=rwX Enrico _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
