Manoj Srivastava <[EMAIL PROTECTED]> wrote: > With the new, streamlined, internal dependency mechanisms, it is > actually going to be a big kludge not to require the configure target > in the dependency path (since the dependency path has been separated > from actual make commands for targets).
Thats fine, now we know that we must provide a .config to call make-kpkg, whereas previously we were occasionally getting away without it isn't a bit deal. Thanks for clarifying why maintaining the old (not to specficiation) behaviour is a pain. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
