On 08/08/2015 03:35, Bruce Korb wrote: > This is necessary. Perhaps if you build on one platform and run on > another, > you might have "issues", but the problem boils down to trying to understand > when some template has wandered out into the weeds. I can pick an > arbitrary > "Oh, I'm certain that doing thus-and-so will _never_ take longer than X." > but that doesn't scale very well. So, I just take a rough measure based on > configure time and then add in a factor of 10 on the theory that it's close > enough and can be overridden anyway.
There are already two bounds hardcoded. How is using a constant in the interval “worse” than that? > >> * timezone-dependant date > > Unclear what part of the patch addresses this. The changes to autoopts/tpl/agman-*.tpl -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
