On Thu, 20 Jul 2006, Andrew Beekhof wrote: > I'm going to have to revert this... it prevents the .py files from > being regenerated when the .py.in ones change
Hmmm... So it does. But using "_PYTHON" feels like the right general approach to pursue. So either I've overlooked a subtlety in following that (my bug), or there might be an automake problem (automake bug). Either way, it would be nice to understand a little more about this problem before (or at least in parallel to) simply reverting it. If it's our (my!) bug, we can fix it. If it's an automake bug, we are honour-bound to report it back to the automake maintainers. (And we (heartbeat) might then need to revert my patch as a local "necessary evil"(*) expedient workaround.) Andrew: let's each generate the two Makefiles corresponding to the two versions of the "Makefile.am", and try to see what their significant difference is. (*) St. Augustine. -- : David Lee I.T. Service : : Senior Systems Programmer Computer Centre : : Durham University : : http://www.dur.ac.uk/t.d.lee/ South Road : : Durham DH1 3LE : : Phone: +44 191 334 2752 U.K. : _______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
