> +Alternatively you can link your python3 to python.
> +`ln -s /usr/bin/python3 /usr/bin/python`
That "to" looks backwards to me. I expect:
link python to your python3
That command line doesn't work on FreeBSD or NetBSD
FreeBSD:
$ which python3
/usr/local/bin/python3
$
NetBSD:
$ which python3
/usr/pkg/bin/python3
$
I have fixed buildprep to include the package that sets up "python"
That's on Fedora, Debian, FreeBSD, and Alpine Linux.
buildprep has some python2 cruft. I ignored it.
Should we announce that it no longer works for python 2 and clean it up a
bit?
-----------
> +If installing to an SELinux enabled system you should perform the
> +following steps. The first line allows systemd to see the units with
> +NTPsec, the second allows the actual executables to run.
Should we fix waf install to do the magic for SELinux?
--
These are my opinions. I hate spam.
_______________________________________________
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
