https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417
--- Comment #59 from Tomás Cohen Arazi <[email protected]> --- (In reply to Jonathan Druart from comment #56) > Can we dedicate this bug report to the base idea, then create bug report on > top of it for experiment? I'd like to avoid noise for testers and keep the > comment list easy to follow. I agree with that. As discussed by other means, my only concerns are: - should we make it opt-in at this stage (i.e. keep the current scripts, but have a config/syspref that defines if the rabbitmq + daemon should be used). As it is packaged in the supported distros/versions it is not *that* important but worth discussing. - I don't agree with pulling the rabbitmq-server package automatically on a Debian install. We don't do that with mysql-server/mariadb-server and we should follow that approach. i.e. on the install notes, there will be an entry, before installing koha-common, which will say 'RabbitMQ' and will explain that if you already have one running, you point to it when calling koha-create (bug 25674) and otherwise what command to run for installing it. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
