machawk1
Associate WARC files on the system with WAIL
via AppleEvents. https://github.com/pyinstaller/pyinstaller/pull/50 seems to imply that it's supported but does not give points to how to specify this at compile time.
Also, http://superuser.com/questions/246476/create-new-extension-association-and-icon-in-snowleopard would allow it to be done manually, like the versioning modification in MAKEFILE.sh.
No dice on manually modifying the Info.plist file, even with modeling it after "The Archive Browser"'s and moving the app to another folder and back (as directed to supposed invoke the Launch Services).
Changes in 0840902d2ea16b6afa973dc67818fba355a0f529 will only associate WARCs on the system if built from source. Still need a way to associate the file type upon binary installation.
LaunchServices usually registers the filetypes supported when dragging an application into /Applications. The current association is in ~/Library/Preferences/com.apple.LaunchServices/com.apple.launchservices.secure.plist and can be manipulated with /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister.
https://github.com/moretension/duti might also be a good way to prevent the bugginess of interacting with LaunchServices. It's also public domain, so should not be an issue for inclusion.