Glenn Burkhardt <[EMAIL PROTECTED]> writes:
> There are quite a few bug fixes in the CVS repository that could help
> folks out - isn't it time for a new release? In particular, I'm still
> seeing reports of problems with POP access that I know were fixed about
> a year ago...
I was hoping to get the new date parsing code back to being as functional as
the previous version (i.e. restoring support for unofficial standard
timezones like JST) before the next release. Also, a more serious problem
in that area was that if textual and numeric offset timezones were both
present (and the textual timezone was ambiguous or conflicted with the
numeric offset), the textual timezone was preferred rather than the numeric
one. Perhaps this has already been fixed -- I haven't had time to check
lately.
Also, since support has been added for linking in a third-party shared
library (Cyrus SASL), I want to get the build process to handle the shared
library path stuff properly rather than silently producing an executable
that fails to run. Right now there's only support for doing that properly
on Solaris. I was going to extend that to other popular OSes, but someone
suggested I was reinventing the wheel and should just include libtool to get
that stuff done. Now that I have the addition of libtool to another package
I work on under my belt, I feel strongly it's the right solution here too.
Since I've just done this recently, it shouldn't take long to do for nmh.
One minor complication is that currently nmh assumes that libtool is an
external program which only exists on Mac OS X. I know the most recent
version of libtool (which came out last week) has improved support for
Darwin -- hopefully it now knows to call the OS's libtool as well on Mac OS
X, so nmh's current OS-X-specific libtool support won't need to be retained.
-----------------------------------------------------------------------
Dan Harkless | To prevent SPAM contamination, please
[EMAIL PROTECTED] | do not post this private email address
SpeedGate Communications, Inc. | to the USENET or WWW. Thank you.
