InstaUp2Date — saves me a step and gives me an extra step…or?

Hi, I'm new to InstaUp2Date. I've created a catalog file (see the end of my post), where I've included the iLife and iWork update vanilla catalogs that comes with InstaUp2Date. Usually I've just kept all of my custom packages in the CustomPKGs folder and numbered them manually in order to install them in the proper order. Now with InstaUp2Date it seems that I have to put the full path to my custom packages in the catalog file as well, when I add a new custom package to my build train, instead of just putting them in the CustomPKG folder prefixed with a number. That seems like an extra step compared to just using InstaUp2Date So I saved a step and I got an extra. Or am I missing something? I would like to install iWork for instance, before running the iWork update (which is in the iWork09_Updates.catalog). Catalog file: ------------------ include-file: 10.6_vanilla.catalog OS Updates: Apple Updates: System Settings: Third Party Software: Software Settings: include-file: iLife09_Updates.catalog include-file: iWork09_Updates.catalog