I'm new to Cyrus imapd - and, for that matter, to autoconf, perl, Linux,
younameit. Building cyrus-imapd-2.1.10 on Mandrake 9.0, I ran into a
problem that people have been running into for years: perl wants to find
modules like Shell.pm under /usr/lib/perl5, but Shell.pm is actually getting
instal
>I believe a set of plaintext documentation can be maintained with RCS,
>CVS or SCCS without problems by a distanced dev team, while XSLT will
>require proper usage by the author manuals etc...
Yep. The reality is it's not us who chose the doc tools, but the people
who actually update the doco.
V
Hi,
> On Sun, 17 Nov 2002 12:35:41 -0500
> Lawrence Greenfield <[EMAIL PROTECTED]> said:
leg+> We'd like to get IPv6 support into 2.2. Would it be possible for you to
leg+> create your patch against the 2.2 branch in CVS?
Oh, it's a great news! Okay, though my patch is against the 2.1
--On Saturday, November 16, 2002 2:10 PM +0900 Hajimu UMEMOTO
<[EMAIL PROTECTED]> wrote:
Hi,
On Wed, 13 Nov 2002 15:57:57 -0500 (EST)
Rob Siemborski <[EMAIL PROTECTED]> said:
rjs3> I'm pleased to announce the release of Cyrus IMAPd 2.1.10. This is
mostly rjs3> a bug-fix and cleanup release,
The critical question is what do you want to accomplish ?
If all you are after is a plain ASCII text copy of the documentation,
then yes plain text is the easiest to maintain.
I think pretty much anything can be maintained at a distance. I am not
sure how one is superior to the other there.
But th
