Some real good news…
I’ve been able to fully qualify Cache Out X for use on Leopard. There were no major path changes that affected the operation of that application. I do need to add a path for the removal of Safari history & cookies, but as it is, those paths are broken under Tiger as well — which is most likely due to changes in Safari 3. I’m also aware of some other browser paths (Opera) that aren’t right which I need to get around to fixing. Bottom line is; while there are a couple of long-standing broken paths, running Cache Out X on your Leopard install is okay to do. I’ll try to get an update out the door by early next week.
Yasu requires a very small change to how the daily, weekly & monthly scripts get run, but aside from that there’s nothing else that needs tweaking. I’ll be updating it either this evening, tomorrow or Friday at the latest (very busy week). In fact, if you wanted to run Yasu 2.1.1 on Leopard until I can get the new version done, it’s totally okay to do. The only thing that won’t work is the weekly cron script. The daily & monthly actually run okay.
There you have it. It’s okay to run Cache Out X and Yasu on Leopard – though a very minor update to Yasu is on the way to fix the weekly cron script from not running, and one on the way for COX to fix browser paths.
Any questions, be sure to use the forums to ask ‘em.
I have two unfortunate results when running Cache Out X under Leopard. First my existing install of 4.7.2 fails with a script error. Second, attempts to install a fresh copy fail with a “run postflight for Cache OUt X failed” message. Hope version 5 is on the way.
Thanks.
Thanks Joe. I’ll be looking into this. Version 5 is on the way…
@Joe – I’ve not been able to reproduce any script error on my end. Can you please post more info in the forums, so I can follow up with you there? Thanks.