I derived the following from the method Michel Fortin uses to create standalone copies of older Safari versions.
- Right click the .pkg file for Safari 3 and ‘show package contents’, and unpack Archive.pax.gz.
- navigate into the new Archive folder. Take Safari.app out of Archive/Applications and place it somewhere.
- Grab all frameworks from Archive/System/Library/Frameworks/ and place them inside Safari.app itself (via show package contents) – create a folder here called ‘Frameworks’
(http://www.michelf.com/weblog/2005/multi-safari/ Explains some of the details from here on out)
- Then use the following script – this is an extract from WebKit CVS which sets the Framework path to the location of the Application bundle itself rather than looking systemwide. Rename Safari.app/Contents/MacOS/Safari to TrueSafari and place this script in that location.
- Make a backup of the Safari.app in /Applications
- Move your new Safari.app to /Applications
This also has the benefit of using the release version of the webkit framework, not the current nightly version, which can cause crashes. As mentioned, you can now use Safari.app normally, without having to bother with webkit.app or do without Safari RSS feed URL handling.