debian packaging

[ghisvail]

Hi Dominique,

Would you be interested in getting pykrylov packaged for Debian / Ubuntu ?

[dpo]

That's an interesting idea. I'm not familiar with the way Debian/Ubuntu package Linux modules though. Don't they use pip and the like?

[ghisvail]

Pip and packaging are actually different beasts.

Pip basically provides a repository for easily sharing code. Any call to pip install triggers a query to the pypl archive, download the latest tarball and attempts a build via the setup script.

Instead, Debian provides a repository of binary packages, i.e. archives that contain pre-built version of software, built from source, for all supported Debian architectures and Python versions.

[ghisvail]

I have successfully done it for linop. Since your setup script is pretty similar to mine, packaging pykrylov for Debian should be fairly easy.

[ghisvail]

It seems that the latest archive available in PyPi (v0.2) does not have any licensing information in it, neither in the distutils metadata nor inside the distribution tarball.

I can only start packaging your work if the licensing terms of your software are clear, i.e. the distutils metadata in PyPi explicitly states your software is LGPL and, most importantly, the appropriate license file is included in the distribution tarball. You can do that by updating your MANIFEST.in file if you have any. Otherwise, you should create one.

[ghisvail]

I'd also advise to ship the source of your documentation within your distribution tarball too. Again, this can be easily done with the MANIFEST.in file.