Where `pyasn1` should be some other name, or maybe `PKG_NAME`
This should be added before this include:
If packaging for Python3, add this after `include $(INCLUDE_DIR)/package.mk`
```
include $(INCLUDE_DIR)/package.mk
include ../python3-package.mk
```
### PKG_UNPACK
Order doesn't matter between `python-package.mk`&`python3-package.mk`.
In many cases, this needs to be overriden. This is usually because the way Python packages are archived, don't follow the convention of other `tar.gz` packages.
These will make sure that build rules for Python or Python3 can be specified and picked up for build.
### Include pypi.mk (optional)
If the package source code will be downloaded from [pypi.org](https://pypi.org/), including `pypi.mk` can help simplify the package Makefile.
So, something like:
To use `pypi.mk`, add this **before**`include $(INCLUDE_DIR)/package.mk`:
It's not important whether this is after or before `include $(INCLUDE_DIR)/package.mk`
`pypi.mk` has several `PYPI_*` variables that must/can be set (see below); these should be set before `pypi.mk` is included, i.e. before the `include ../pypi.mk` line.
### Include python[3]-package.mk
`pypi.mk` also provides default values for `PKG_SOURCE` and `PKG_SOURCE_URL`, so these variables may be omitted.
If packaging for Python, add this after `include $(INCLUDE_DIR)/package.mk`
```
include ../python-package.mk
```
One variable is required:
If packaging for Python3, add this after `include $(INCLUDE_DIR)/package.mk`
* `PYPI_NAME`: Package name on pypi.org. This should match the PyPI name exactly.
For example (from the `python-yaml` package):
```
PYPI_NAME:=PyYAML
```
These variables are optional:
* `PYPI_SOURCE_NAME`: Package name component of the source tarball filename
Default: Same value as `PYPI_NAME`
* `PYPI_SOURCE_EXT`: File extension of the source tarball filename
Default: `tar.gz`
`pypi.mk` constructs the default `PKG_SOURCE` value from these variables (and `PKG_VERSION`):