I can't see how it would be justified to put 2 gigabytes of unwanted junk on your HD just for one measly UNIX manpage. I guess the SetFile command is a barebones utility command and so the instructions are embedded in the file.
When the Xcode installer runs, one of the many things it does is to change the command search path(s) to command files. With Xcode installed, you don't need to specify the entire path to the command like I did above. You can set your path persistently but it's not something a beginner would do.
In any case, I had written an Applescript to look for the location of SetFile and install it if not already. It looks like this:
(some parts may not work anymore)
--
http://Gnarlodious.com/Apple/AppleScript/
-- version 12/20/2004
property fileUtilityPath : "/Developer/Tools/SetFile"
set SetFileURL to "http://corz.org/osx/soft/stuff/setfile.gz"
-- is Xcode installed?
do shell script "ls Developer/Tools/SetFile"
if (do shell script "ls " & fileUtilityPath) = "" then
display dialog "Xcode is not installed"
set fileUtilityPath to "ls /usr/local/bin/SetFile"
if (do shell script "ls " & fileUtilityPath) = "" then -- if the SetFile utility is not found, install it
display dialog "Error... SetFile not found" & return & "Please install the SetFile utility to enable changing the file creation date" buttons {"Download it", "Quit"} default button 1 with icon caution
if the button returned of the result is "Download it" then
-- download and install the file ... NO ERRORCHECKING HERE!
do shell script "curl " & SetFileURL & " > $HOME/Desktop/SetFile.gz"
do shell script "gzip -d < $HOME/Desktop/SetFile.gz >> $HOME/Desktop/SetFile ; mv $HOME/Desktop/SetFile /usr/local/bin ; chown root:admin /usr/local/bin/SetFile;sudo chmod 775 /usr/local/bin/SetFile" with administrator privileges
else if the button returned of the result is "Quit" then
return
end if
end if
end if
-- further script to do whatever with file dates