On 16 Jul 2000, Russ Allbery wrote:
> My macro instead does *tzname = "UTC". I'm not aware of any platform that
> uses these variables but doesn't allow the user to modify them, so that
> seems to work.
Seems reasonable, but the fact that you have to wonder in the first place
makes this the seemingly less portable solution.
> Currently in INN and not in autoconf:
>
> - Finding BerkeleyDB and OpenSSL and setting up an appropriate
> compilation environment (libraries, headers, etc.) as necessary.
Me too.
> - The installed version of Perl.
Me too.
> - The flags necessary for building with an embedded Perl or Python
> interpreter.
Me too.
> - Whether there's a tm_gmtoff in struct tm, and if not whether there are
> external timezone and daytime variables.
Me too.
> - int32_t and uint32_t, if not provided by the implementation.
Me too.
> - Working inet_ntoa.
Me too.
"Me too" here means mostly "I could really use this; I have already
written some of these myself."
In particular I'd like to see a more generalized approach to "find out
whether package X is available and how" (re OpenSSL etc.). Currently,
every package rolls its own interface.
Seems like we got our work all laid out for us... :-)
--
Peter Eisentraut Sernanders vaeg 10:115
[EMAIL PROTECTED] 75262 Uppsala
http://yi.org/peter-e/ Sweden
