Ultamatix

Testing code block area:

echo “Beginning build of “$FILE
echo “=================================”
echo “Relaxing permissions of “$FILE
sudo chmod -R 777 $FILE/
sudo chown -R $USER:$USER $FILE/
echo -e “${bldgrn}Cleaning up any tmp or backup files.”
find $FILE/ -type f -name “*~” -exec rm -f {} \;
echo “Setting individual file permissions to 644.”
find $FILE/ -type f -exec chmod 644 {} \;
echo “Scanning for executables in “$FILE”/”
cd $CURRENT
#Test for executables & make naming conventions apply spaces etc.
#/usr/share/screenlets/Lyrics/Quodlibet plugin/LyricsScreenletInformator.py becomes /usr/share/screenlets/Lyrics/Quodlibet\ plugin/LyricsScreenletInformator.py to set the executable bit.
#Sed is hardcore, also handles many other nonstandard characters all in one line. Why? Because I sed so
#first find executables and set executable.
find $FILE/ -name “DEBIAN” -prune -o -type f -exec sh -c ‘test “$(head -c 2 “$1″)” = “#!”‘ sh {} \; -print -exec chmod 755 {} \;
#No header, no problem
#find $FILE -name “*.sh” -exec chmod 755 {} \;
#find $FILE -name “*.py” -exec chmod 755 {} \;
#Nonstandard? spaces ( ” etc. sed ‘s/\([ "(){}$#\&~'"'"']\)/\\\1/g’
cd $FILE/


This should be code