2.4.6 and /usr/sbin/cyrus

[Anthony Prades]

> On Mon, Dec 20, 2010 at 5:52 PM, Ondřej Surý <ondrej at sury.org
> <mailto:ondrej at sury.org>> wrote:
>
>     Hi all,
>
>     I have pushed my repository to alioth which introduces two major
>     changes:
>
>     - Introduction of versionless virtual packages (ie. cyrus-imapd
>     depending on cyrus-imapd-2.4, etc.)
>
>     - New /usr/sbin/cyrus tool (which is just crude shell script right
>     now) which "knows" all the cyrus commands located in
>     /usr/lib/cyrus/bin/*
>
>     I have tried to preserve backwards compatibility (installing symlinks
>     everywhere) with our old cyrus-imapd-2.2, but anyway this is a change
>     which needs to be discussed with upstream. Jeroen, what do you think
>     as a release manager? Is the /usr/sbin/cyrus a way which could
>     possibly be adopted by upstream? (I was also thinking about calling it
>     just 'cyr', but there is a name clash with console-cyrilic package
>     :-(.)


Hi,

I like this way, but if this isn't an upstream feature, it will be better to 
keep backwards compatibility as you done. If so, we got 2 commands to the same 
thing (old command and using wrapper which was a Debian specificity). Doesn't it 
confusing to administrators ?

If this is included in upstream - or we remove backwards compatibility, we need 
to upgrade 'cyrus.conf', at least to get database auto-upgrade success on Cyrus 
startup, otherwise you will crash you BDB databases, so you need a backup of the 
old datas.

Anthony

>
>     I tried to follow the git path as much as possible (manpages are
>     renamed to cyrus-{something}) and the script tries hard to find the
>     relevant command (it automatically prepends cyr_{command} and
>     ctl_{command} and knows the check = chk_cyrus). More tweaks can be
>     added later (f.e. we can introduce cyrus control {subcommand} to call
>     /usr/lib/cyrus/bin/ctl_{subcommand}).
>
>     Again I have finished this just before my end of worktime, so it just
>     builds in the pbuilder. Brave hearts are welcomed to test the result
>     using git-buildpackage. I do not guarantee anything, it may eat your
>     system or your dog :).
>
>