Norman,
> I know that at least some packages do nonetheless call [hlink], and
> that there's an argument for it. Perhaps then these packages should
> declare a dependency on htx.
That would seem to be the most transparent solution.
> Hmm, htx is listed as depending on star2html, but that's only because
> the htx configure.ac declares STAR_LATEX_DOCUMENTATION(sun188), which
> includes that dependency automatically. If that line were to be
> removed, then SUN/188 wouldn't be installed by default (big deal), but
> we would then be free to declare a (fake) dependency of star2html on
> htx, which would be enough to cause htx to be built and installed
> first. How does that sound?
Should we not be up-front about dependencies, and state dependencies on
htx where they exist rather than relying on a hidden away back-door
approach?
Having just grepped for hlink, the only components which depend on htx
seem to be ast, kaplibs and echomop. Would it not be simpler just to add
a build dependency on htx to each of these three components?
David
|