Re: Add support for generating HTML docs a` la PDF, etc., revision2

[Alexandre Duret-Lutz]

>>> "Richard" == Richard Dawe <address@hidden> writes:

 Richard> Hello.
 Richard> Alexandre Duret-Lutz wrote:
 >> Sure, having to revise one's Makefile.am on Automake upgrades is
 >> a pain.  I don't really see what else we could do.  (Never
 >> introducing new targets doesn't look like a solution to me.)  It
 >> sounds like we ought have diagnostics to help the transition by
 >> spotting such troublesome rules.  How would we catch these?
 >> Right now the only thing I can think of is to add something
 >> like:
 >> -Woverride Warn when a user rule override an Automake rule

 Richard> Do they actually override? 

Yes:

|    A target defined in `Makefile.am' generally overrides any such
| target of a similar name that would be automatically generated by
| `automake'.  Although this is a supported feature, it is generally best
| to avoid making use of it, as sometimes the generated rules are very
| particular.
| 
|    Similarly, a variable defined in `Makefile.am' or `AC_SUBST''ed from
| `configure.in' will override any definition of the variable that
| `automake' would ordinarily create.  This feature is more often useful
| than the ability to override a target definition.  Be warned that many
| of the variables generated by `automake' are considered to be for
| internal use only, and their names might change in future releases.

 Richard> Does make choose the first or second occurrence of the
 Richard> rule? 

There is only one occurrence: the user's.

 Richard> Is it deterministic? Or does it depend on the make
 Richard> program?

 Richard> How about:

 Richard> -Wclash Warn when a user rule clashes with an Automake rule

Fine.
-- 
Alexandre Duret-Lutz