Packaging instructions for Debian, Ubuntu, etc.

• I have searched the issues of this repo and believe that this is not a duplicate.

Issue

Trying to package poetry for Debian, it is unclear what needs to be done. Usually Python packages come with a setup.py which makes packaging straightforward – but this package does not.

Next stop is the Makefile. Looking at it, it seems like poetry is using poetry to build itself, which creates a circular dependency.

Since the Debian build machines are not allowed to download stuff from the internet at build time, all the vendored dependencies must be in the source tree before the build starts. The package maintainer will probably include it in its version of the source tree.

So I assume what needs to be done in order to bootstrap is:

• have one command to fetch all dependencies
• install dependencies
• use something like $ python -m poetry.console build to break the circular dependency and use poetry from the source tree?

If that is correct, it would be nice to have one command that downloads all dependencies poetry needs to bootstrap itself (but does not install them or poetry immediately).

[sinoroc]

@venthur Thanks to PEP517 it is pretty standardized now. As @abn mentioned you might want to look at PyPA’s build tool and PEP 517 in general, so that you can solve the packaging process once and for all for all projects that use a PEP 517 conform builder (instead of solving just for one project: poetry).

[abn]

I am going to close this as it seems the original question has been answered.