I would imagine you'd all agree that actual build dependencies go farther than that: plugins would probably be really hard to deal with in this kind of framework.
Has anyone given thought or have a solution to the problem of expressing all possible dependencies in a page build? I'm thinking of the situation of static builds and Makefiles.
In this case, the useful thing would be to efficiently emit a list of dependencies without actually generating the targets. Kind of like 'gcc -M', if you get my drift...
I would assume that any plugin that used an input file would have to be hooked into whatever scheme was used.
It all seems kind of insuperable, really, since we're dealing with an interpretive language here, but I'd like to hear how/if others have dealt with this issue.
--
Why waste time learning when ignorance is instantaneous?
-- Hobbes
_______________________________________________ templates mailing list [EMAIL PROTECTED] http://lists.template-toolkit.org/mailman/listinfo/templates
