Executing(%install): /bin/sh -e /home/guillaume/rpm/tmp/rpm-tmp.42320 + umask 022 + cd /home/guillaume/rpm/BUILD + cd xml-stylebook + install -d 755 /home/guillaume/rpm/tmp/stylebook-buildroot/usr/share/java + install -d 755 /home/guillaume/rpm/tmp/stylebook-buildroot/usr/share/stylebook + cp bin/stylebook-1.0b2.jar bin/stylebook-1.0b3.jar /home/guillaume/rpm/tmp/stylebook-buildroot/usr/share/java + cp -R styles/apachexml styles/christmas styles/ibm-style /home/guillaume/rpm/tmp/stylebook-buildroot/usr/share/stylebook [guillaume@silbermann guillaume]$ ll rpm/tmp/stylebook-buildroot/usr/share/stylebook/ total 2 drwx------ 6 guillaum guillaum 192 aoû 7 16:29 apachexml/ drwx------ 6 guillaum guillaum 288 aoû 7 16:29 christmas/ drwx------ 6 guillaum guillaum 192 aoû 7 16:29 ibm-style/ Why are the perms directories like this, while umask 022 is forced at the beginning of the install stage ? Question: install allows fine tuning over created file perms, while cp doesn't. However, is there a simple way to process a recursive install command ? -- Guillaume Rousse <[EMAIL PROTECTED]> GPG key http://bohm.snv.jussieu.fr/~rousse/gpgkey.html
