Re: how to make cook detect if it is in a change set or not

Found a hacked workaround (can someone tell me if there is something better):

/* Have to use #ifdef and not if[defined ...] because #includes get
processed before the second */
#ifdef search_path
        search_list=[split ":" [search_path]];
#else
        project=foo;
#endif

...

/* This only works if -bl is given on aetar */
if [defined change] then {
        project_files = [collect_lines aelpf -p [project] -c [change]];
        change_files = [collect_lines aelcf -p [project] -c [change]];
        manifest = [stringset [project_files] [change_files]];
} else {
        manifest=[stripdot [collect find .]];
}





On Sun, Jul 7, 2013 at 6:19 PM, Aryeh Friedman <[email protected]> wrote:
> I have a program that gets given out in source form and it uses cook
> as the DMT... I am using aelcf/aelpf to make the manifest but do not
> want to require the installing user to open a change set (or even have
> aegis installed) ... what is a quick and dirty way to detect if it is
> being called from within a change set and thus ues aelcf/aelpf or not
> and thus use find?