[Twisted-Python] Building Twisted 13.2.0 packages for RH 7.0
Hi, I need to build twisted 13.2.0 packages for RH 7.0. I downloaded the source from https://pypi.python.org/packages/source/T/Twisted/Twisted-13.2.0.tar.bz2#md5.... Currently, I'm able to build only one package "python-twisted-13.2.0-1.x86_64.rpm" (by running the command "python setup.py bdist_rpm") which contains all the sub-projects. How can I build separate package for each twisted sub-project (e.g. conch, core, mail, web, etc...)? I would like to have the following twisted packages at the end: python-twisted-13.2.0-1. x86_64.rpm python-twisted-conch-13.2.0-1.x86_64.rpm python-twisted-core-13.2.0-1.x86_64.rpm python-twisted-lore-13.2.0-1.x86_64.rpm python-twisted-mail-13.2.0-1.x86_64.rpm python-twisted-names-13.2.0-1.x86_64.rpm python-twisted-news-13.2.0-1.x86_64.rpm python-twisted-runner-13.2.0-1.x86_64.rpm python-twisted-web-13.2.0-1.x86_64.rpm python-twisted-words-13.2.0-1.x86_64.rpm The main reason is that some packages depends on twisted sub-projects, and therefore, their installation fail (e.g. python-txzmq requires python-twisted-core). Regards, ----------------------------------------------------------------------------------------------------------------------------- Kobi Bar Staff SW Engineer, Cloud Solutions Mellanox Technologies 13 Zarchin street Raanana, Israel +972-74-7129166(o) +972-50-3135001(c) +972-74-7129111(f) www.mellanox.com<http://www.mellanox.com/>
On Nov 3, 2015, at 8:16 AM, Kobi Bar <kobib@mellanox.com> wrote:
I need to build twisted 13.2.0 packages for RH 7.0.
Why do you need to do this? Twisted 13.2 is 2 years old at this point, and is missing important features (especially client TLS verification, added in 14.0). Unless you are upgrading an application that uses older versions of Twisted, you should use the latest version, 15.4 as of this writing.
How can I build separate package for each twisted sub-project (e.g. conch, core, mail, web, etc…)?
In Twisted 15.3, we stopped shipping sub-projects, so in preparation for that you should build your packages to depend on Twisted as a whole. One way to do this more easily is to not build packages, but rather to deploy your application into a virtualenv; since subpackages were never really part of dependency trees on PyPI, only in operating system vendor packages, this should be less of a problem there. I don't actually know how to build RPMs, so I am not holding out on you in terms of how to do it :-). But if you're not Red Hat yourself, it seems like this is a less and less popular way of integrating applications, and for good reason. -glyph
participants (2)
-
Glyph Lefkowitz -
Kobi Bar