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 :-)
aja@ ran into "Found package with different name that compares equal
in /exopi-cvs/ports/plist/amd64: nut-2.8.0pre20220312" - pkg_check-version
doesn't warn but you can't mix XXrc and XXpre.
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.
Follow the upstream recommendations for packagers and switch to
multi-packages:
devel/gettext -> devel/gettext,-runtime
devel/gettext-tools -> devel/gettext,-tools
(new) devel/gettext,-textstyle
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
of the large number of UNSUPP messages, but precisely because of them:
all those .sp requests inside tables are completely pointless and
only spew gratuitious blank lines with groff. Besides, mandoc is
more reliable than groff with respect to the special characters
used when it comes to -Tascii output.
The about 25 broken .so files are already commented out in the
PLIST, and none of them are needed on OpenBSD, all the names are
in the NAME sections anyway.
So drop USE_GROFF and bump those three of the four subpackages
that contain manual pages.
- Install libupsclient headers/pkgconfig files. landry@ asked about
these; they needed a --with-dev configure flag to get them installed...
- Get rid of the useless ${NUT_USER} and ${NUT_ID} SUBST_VARS which are
now getting in the way of new files in the PLIST.
- Move some files from /usr/local/share/ups to a more easily recognisable
/usr/local/share/nut.
