MODPY_PYBUILD={setuptools,...} instead of outdated MODPY_SETUPTOOLS=Yes.
Also remove instructions for python2-only ports as new ports are
expected to be python3(+?) now.
with input and ok sthen@
skeleton script for people who want to override FETCH_CMD but don't
know exactly what ftp(1) options pkg_add/bsd.port.mk/dpb are going to
want.
A bit of feedback from sthen@, more to come most probably
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.
With this a port can be easily generated for Go applications that support Go
modules (there will be a go.mod file in the root of the project).
For example: https://github.com/jrick/domain/blob/master/go.mod
The mod file lists "github.com/jrick/domain" as the module name, so a portgen
command to build the above tool would be:
portgen go github.com/jrick/domain
OK afresh1@ kmos@
MODPY_VERSION to /usr/ports/infrastructure/templates/Makefile.template.
These are the most common entries that portgen(1) will throw at the
bottom of a generated python port because it doesn't know where it would
go. Adding these will have portgen(1) put them in the appropriate place.
Comment tweaks and ok sthen@
- mention that COMMENT usually starts lower-case
- COMPILER for C++ ports
- mention use of CONFIGURE_STYLE=none to override default from a module
- example do-gen/BUILD_DEPENDS for autogen.sh-type ports
ok kn@, ok/typo fix pamela@
rsadowski