Hello,
I am using Fedora17 and a rpm version of roundcube.
On this rpm packaging, configuration main.inc.php and db.inc.php are both stored in /etc/roundcubemail/
Also, I use the managesieve plugin and I have to modify the plugin port from 2000 to 4190 in the plugin configuration setting (/usr/share/roundcubemail/plugins/managesieve/config.inc.php)
As the RPM package updates from time to time, the config.inc.php gets overridden.
I have without success to set the port in the main.inc.php.
Is there a standard way or a best practice to set $rcmail_config['managesieve_port'] = 4190; in /etc/roundcube/..... that allows to override any previous setting?
Thanks,
Le 10/11/2012 20:31, Jordi Llonch a écrit :
Hi,
Probably the RPM you're using is not well designed. If a rpm has a file tagged as config file, it should not be overwritten when upgrading.
you can do rpm -qcp my_package_file.rpm to list the config files in it.
If you can not see all config files included in the package, then the package maintainer should consider using the %config macro when making the spec file of the package.
regards,
different config from managesieve port is only a part of dovecot config
Le 2012-11-10 20:31, Jordi Llonch a écrit :
On Nov 11, 2012, at 4:09 AM, roundcube ml@roundcube.fakessh.eu wrote:
Ive always wondered why the managesieve plugin uses 2000. Iana defines the default port as 4190, and dovecot uses that default port. But, the fedora package is broken if it overwrites the config file.
You can just add $rcmail_config['managesieve_port'] = 4190; to /etc/roundcubemail, and comment out that line in the plugin directory. But you'll have the same problem, a new package will overwrite the plugin config file and remove the comments.
I guess the only option (besides fixing the rpm) is to make your own plugin that sets config options, and load that plugin last. That's only a few lines of code, trivial really.
Cor
Hello Cor,
It is a good proposal.
The solution will cause more processing involved for every webmail hit.
I think the right approach should be the main.inc.php file to be able to read the configuration and if a key is set, not to be overriden by plugins config.
Any better ideas or suggestions?
Jordi
2012/11/11 Cor Bosman cor@xs4all.nl
On Nov 11, 2012, at 9:05 AM, Jordi Llonch llonchj@gmail.com wrote:
I dont see it happening the way you describe. Theoretically I suppose every plugin could check if a certain config value already exists, and if so, not reset it, but that also causes more processing. Normally this isnt an issue, as the plugin config file should not be overwritten. That is the actual problem. Maybe write to whomever makes that rpm, and tell them to make sure the plugin config files dont get overwritten.
Like I said, right now, while waiting for the rpm to get fixed, your only option is to make your own plugin and load it last. This could work for multiple plugins in 1 go. I dont see another option.
Cor
It shouldnt be so hard to fix the rpm. Normally the plugin comes with a config.php.dist file, and im sure the rpm creator wants to make sure the plugin is in a working state and so they added the actual config.php. That's fine. What they can do is make a post install script that checks if there is a config.php, and if not, create one. If it does exist, it leaves it alone. Problem solved.
Cor
-
Cor Bosman -
Jordi Llonch -
roundcube -
Sébastien BLAISOT