I believe this was discussed a few months back, and was decided that the packages should remain horde2/imp3 for compatability purposes.

If they change to horde/imp will that not create issues for pre 9.2 users that already have the horde suite configured & installed? (Not to mention making things much more confusing.)

Thanks,

S

Guillaume Rousse wrote:

I just rewieved the whole horde suite:
- horde2
- imp3
- turba
- chora

It seems old imp 1 or 2 are no longer around, while there is still old horde-nag 1. Could we nuke it, and turn horde2 to horde and imp3 to imp ?

BTW, i found the ADVX macros very useful. Why are those macros in /usr/share/ADVX, and not integrated among standard rpm macros ?

I also found most private directories are both protected by the in apache config file, and by a local .htaccess in the directory. Isn't this a bit redundant.

Finally, all those sensible files (apache config file, .htaccess files) are owned by apache groupe, with 640 perms, which make rpmlint scream. Time for some new rpmlint exception/check ?







Reply via email to