@jacknagel That *almost* worked but had 1 flaw. In either context (devel or normal) brew will use the same filename for the resource in the `brew --cache` directory. So if you have a devel version of the resource in your cache from a previous installation, and try to do a normal install with the resource included, brew tries to use the file in `brew --cache` which fails the sha1 check because it's the wrong version.