cook: best way to handle commands that normally fail

--===============7309203356887517139==
Content-Type: multipart/alternative; boundary=047d7b672dfae9826e04f31fb237

--047d7b672dfae9826e04f31fb237
Content-Type: text/plain; charset=ISO-8859-1

I need to diff some files against the installed ones during the cooking of
a project... in new installs this means they are always different (exit
code 1) how do I get cook to ignore this without resorting to set errok?

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org

--047d7b672dfae9826e04f31fb237
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr">I need to diff some files against the installed ones during the cooking of a project... in new installs this means they are always different (exit code 1) how do I get cook to ignore this without resorting to set errok?<br clear="all">
<div><br>-- <br><div dir="ltr">Aryeh M. Friedman, Lead Developer, <a href="http://www.PetiteCloud.org" target="_blank">http://www.PetiteCloud.org</a><br></div>
</div></div>

--047d7b672dfae9826e04f31fb237--

--===============7309203356887517139==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KQWVnaXMtdXNl
cnMgbWFpbGluZyBsaXN0CkFlZ2lzLXVzZXJzQGxpc3RzLmF1dWcub3JnLmF1Cmh0dHBzOi8vbGlz
dHMuYXV1Zy5vcmcuYXUvbGlzdGluZm8vYWVnaXMtdXNlcnMK

--===============7309203356887517139==--