Glad to apport my two cents for Cyrus.
Excuse me and please tell me if I'm doing wrong
posting it to the list, maybe one should
sent the patches to another place.
Just to point thay you may want to correct
the description of the patch at the top of the file,
the first reference to the configuration file to
be edited refers erroneously to cyrus.conf(5)
instead of imapd.conf.
And as a bonus a question (for the mailling list):
I'm maintaining RPM packages for Red Hat Linux of
Cyrus IMAPd, and I'm giving the final retouches to
the package containing version 2.0.12.
Here is the situation (I hope being clear enough with
my bad english):
1) Now that drac support is selectable at runtime
I want to be able to make incorporating the
drac patch at build time a choice for the builder
(he/she should have libdrac.a available in the filesystem
at this point).
2) Right now the package build process is using configure
as it comes with the Cyrus IMAPd distribution.
3) the drac patch needs to rebuild configure from
the patched configure.in, so it adds two (possibly
three?) new packages to the list of build
dependencies: (automake autoconf (and smake?)
I was trying to avoid this and come to the
following solution:
install automake, autoconf (and smake?) on my system
unpack the Cyrus IMAPd distribution to dir A
unpack the Cyrus IMAPd distribution to dir B
apply the drac patch to dir B
run
# rm -f aclocal.m4 configure ; sh SMakefile
on dir B
An now obtain a new drac patch by running
diff -ruN A B
This new drac patch is applied in the %prep
section of the specfile. a diffstat -w 50
run on it gives now:
acconfig.h | 3
config.h.in | 3
configure | 511 +++++++++++++------------
configure.in | 15
imap/imapd.c | 52 ++
imap/pop3d.c | 13
man/imapd.conf.5 | 7
7 files changed, 378 insertions, 226 deletions
(the high change count in configure is because many
"echo configure:<line number>" changes after
insertion os some lines on it)
I'm doing this because the 'expected audience' for the RPM
packages is people running Red Hat Linux (as I do), 7 and
even the coming 7.1 each one with potentially different
versions (or none at all) of db3 and cyrus-sasl
so I'm recommending people to download and rebuild
the source RPM in their system rather to use the binary
one made in my system. But I want to avoid, if
possible, to force them to install autoconf,
automake (and smake).
Is it correct or I'm making some wrong assumption(s) ?
TIA !
Ken Murchison <[EMAIL PROTECTED]> wrote:
> Thanks for the changes.
>
> I have attached a slightly modified version of your patch for 2.0.12. I
> have also checked a similar patch into CVS for inclusion with future
> releases.
>
> My changes:
>
> - Use value of 'dracinterval' to enable/disable DRAC at runtime.
>
> - Set the default value of 'dracinterval' to 5, since I think that most
> people who compile Cyrus with DRAC support will tend to use it and
> expect it to be on.
>
> - Disable DRAC at runtime if dracd can not be contacted.
>
> Ken
>
>
____________________________________________________________________
Get free email and a permanent address at http://www.amexmail.com/?A=1
