If we need to make an exception we can do it and properly document the
reason but by default we should just use the default login class.
rc.d uses daemon or the login class provided in login.conf.d so this has
no impact there.
discussed with sthen@, tb@ and robert@
praying that my grep/sed skills did not break anything and still
believing in portbump :-)
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.
lang/python port module. I've not yet come up with a port that
would not need this and one can always set MODPY_TESTDEP to "no"
to prevent the module from touching TEST_DEPENDS.
Idea from afresh1 who pointed out the cpan module already does this.
aja "I support this move."
OK sthen@
- use a separate _barman:_barman user/group
- use /var/db/barman as the default datadir, setting appropriate
permissions (ie _barman:_barman / 750)
- make ${SYSCONFDIR}/barman.conf root:_barman & mode 640
- add README teaching how to configure _barman's crontab
Join work with Jean Gerard Pailloncy, tweaks & ok ajacoutot@
Barman (backup and recovery manager) is an administration tool for
disaster recovery of PostgreSQL servers written in Python. Barman can
perform remote backups of multiple servers in business critical
environments, and helps DBAs during the recovery phase.
Barman's most wanted features include: backup catalogues, retention
policies, remote recovery, archiving and compression of WAL files and
of backups.
ok ajacoutot@
