I don't think you should do that ... The simple option would be a script edyuk_macx with export and open. Then, for each file release, you should build bundle embedding all libraries using otool and install_name_tool.

Persons checking your trunk out know how to launch edyuk without any script whereas final users just wanna drag and drop edyuk into their application folders or wherever else. This is why each release should be correctly packed the way it is mentionned in the deployment documentation and proposed in the forge file release system. Preparing the bundle is just a question of 5 minutes ...