> In the case of update files, the source depends on them. > (Most 'make' driven packages do not employ anything as sophisticated > as CMS UPDATE. Some do use 'patch'.) What we would need is the > "make depend" kind of thing that was already mentioned. What CMS Make > then needs for that is the ability to append dependencies to a > previously established recipe.
Consider the X 'xmkmf' approach, where there's a site-wide configuration that is substituted into a template provided with the app, and the app template supplies things like specific library lists and control file lists.
