On Mon, 25 Nov 2002, Jonathan Marsden wrote:
> On 25 Nov 2002, Rob Siemborski writes:
> > On 25 Nov 2002, Erik Enge wrote:
> This is in part a packaging and upgrading issue, though. Especially
Detecting the backends and running a script or program when the backends
changed is simple enough for my
Tarjei Huse schrieb:
>
> <(snip)>
> > > 'worse' as new backends are implemented, the ability to build a
> > > compiled version of Cyrus that could find and use whatever database
> > > format it can see (or failing that, whatever database some separate
> > > utility can see and then edit into the c
<(snip)>
> > 'worse' as new backends are implemented, the ability to build a
> > compiled version of Cyrus that could find and use whatever database
> > format it can see (or failing that, whatever database some separate
> > utility can see and then edit into the config files), would probably
> > h
Jonathan Marsden schrieb:
>
> On 25 Nov 2002, Rob Siemborski writes:
>
> > On 25 Nov 2002, Erik Enge wrote:
>
> >> I wouldn't rate it as easy unless it was a config option at
> >> run-time, not an option to configure at compile-time.
>
> > This wouldn't be tremendously hard to do (probably just
On Mon, 25 Nov 2002, Jonathan Marsden wrote:
> This probably isn't something of great utility to CMU, but for the
I think you hit the nail on the head here.
> average Linux sysadmin who just wants to grab an RPM or a .deb and
> install it and have Cyrus "just work", upgrading as new RPMs/.debs a
On 25 Nov 2002, Rob Siemborski writes:
> On 25 Nov 2002, Erik Enge wrote:
>> I wouldn't rate it as easy unless it was a config option at
>> run-time, not an option to configure at compile-time.
> This wouldn't be tremendously hard to do (probably just a matter of
> replacing some macros with som
