2013/12/20 Michael Fladischer <[email protected]>: > Because celery can be used without the init scripts. In the > environments where I run celery, it is used to power workers for more > than one project per OS instance. The init scripts are only a > convenience feature to get beginners started who only run a single > project.
The main problem here is we are going to introduce a new binary package, whose debianization is bigger in size than the init scripts themselves. Normally, new packages are introduced to separate big dependency chains, or to provide segregation between services os features. I think this case doesn't match one of the above. > Production environments would usually run python-celery with the > workers managed by supervisord. Those environments can now just skip > the celeryd package and avoid cluttering their init system with > scripts they won't use. As long as the init script is disabled by default, I don't think that will be a problem. Another approach would be to provide the init files as examples, and not in the init.d directory. Cheers, Luca _______________________________________________ Python-modules-team mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
