pypi-pkgbuild is a PKGBUILD generator using the metadata found in Python packages uploaded to PyPI.
How to use
Just launch the script with the name of the packages you want to get a PKGBUILD for :
$ pypi-pkgbuild jinja2 werkzeug pygments Locating and fetching the 'jinja2' distribution Extracting and fetching the metadatas Generating the Archlinux PKGBUILD Generated a PKGBUILD for 'python-jinja2' in 'python-jinja2/PKGBUILD' Locating and fetching the 'werkzeug' distribution Extracting and fetching the metadatas Generating the Archlinux PKGBUILD Generated a PKGBUILD for 'python-werkzeug' in 'python-werkzeug/PKGBUILD' Locating and fetching the 'pygments' distribution Extracting and fetching the metadatas Generating the Archlinux PKGBUILD Generated a PKGBUILD for 'python-pygments' in 'python-pygments/PKGBUILD'
Be careful, as they are auto-generated PKGBUILDs they may contain errors. The most common errors are the following :
- The script assumes all Python packages are named python-packagename. This may not be true : for example, Django is packaged as django and not python-django. You must manually modify the dependency list to modify this kind of errors.
- The dependencies may not be packaged. You must check if they exist on the AUR or in the main repositories before uploading the package.
- The license field may not contain a normalized value. You must check this value to be sure it complies to the Archlinux packaging standard.
There are also features which are not yet handled by the script, like md5sums generation. Just use makepkg -g to generate them.
How to report a bug
Browse to the new issue tab and fill the form. Please report any unusual behavior you may encounter as well as errors which should not occur.