if a port needs 2.x then set MODPY_VERSION=${MODPY_DEFAULT_VERSION_2}.
This commit doesn't change any versions currently used; it may be that
some ports have MODPY_DEFAULT_VERSION_2 but don't require it, those
should be cleaned up in the course of updating ports where possible.
Python module ports providing py3-* packages should still use
FLAVOR=python3 so that we don't have a mixture of dependencies some
using ${MODPY_FLAVOR} and others not.
even with BROKEN set in the port) so commit my incomplete work updating to
3.8 branch. still marked BROKEN as it will need some work from somebody
interested in this as it was dying shortly after startup.
- build & install manual pages;
- provide default HOME= line in rabbitmq-env.conf, allowing rabbitmqctl
to work out-of-the-box, including rcctl check/stop cases.
parameter to daemonize, move the parameter from daemon to daemon_flags,
so that the user cannot inadvertently prevent it from daemonizing by
adjusting the flags.
Discussed with ajacoutot and schwarze, this method was suggested
by schwarze@ as a simpler alternative to my diff. ok aja@
- simplify rabbitmqctl diff, use su to make sure command is run as ${RABBITUSER}
- change _rabbitmq shell to /sbin/nologin,
- remove redundant setting of PYTHON,
- remove unnecessary SUBST_CMD calls,
- remove trailing space in MAKE_ENV.
discussed with maintainer and ajacoutot@
tweaks by me (don't silent SUBST_CMD, no need to cvs rm/add
files/rabbitmq.conf as it can be installed with the correct name)
- add rc script, remove pkg/MESSAGE
- fix rabbitmqctl args passing
- install config file as rabbitmq-env.conf
Needed by an upcoming erlang update..
Maintainer timeout, Piotr Sikora takes maintainership.
ok stuartslolbunny@ (!?)
RabbitMQ is a complete and highly reliable Enterprise Messaging
System. The RabbitMQ client libraries and broker daemon can be used
together to create an AMQP network, or used individually to bring
the benefits of RabbitMQ to established networks.
ok bernd@
