如何为 twind/twisted 插件制作 ubuntu/debian 包？
作为 如何为与 setuptools、distribute 等一起使用的 twind/twisted 插件编写 setup.py？，如何为twisted 插件制作 debian 包？
假设 setup.py 编写正确，使用 cdbs/python-central/dh_python2 应该可以工作，但到目前为止我还没有太多运气。
这些工具的技巧在于，它们基本上运行“python setup.py install --root=”，然后打包“”中的所有内容，所以也许一旦正确回答了前面的问题，那么这个问题就变得毫无意义了？
这里有人成功打包了 debian 的twisted 插件吗？
As a follow-up to How do I write a setup.py for a twistd/twisted plugin that works with setuptools, distribute, etc?, how does one make a debian package for a twisted plugin?
Assuming the setup.py is properly written, using cdbs/python-central/dh_python2 should just work, but I haven't had much luck so far.
The trick with those tools is that they basically run 'python setup.py install --root=' and then package up whatever ends up in '', so perhaps once the previous question is properly answered, then this question becomes moot?
Anyone here has successfully packaged a twisted plugin for debian?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
显然，问题出在“python-support”上，当涉及到扭曲的插件时，它就完全被破坏了。
来自 Ubuntu 的 Matthias Klose 的这条消息解释了该问题并提供了解决方案解决方案：
Apparently the issue is with 'python-support', which is plain broken when it comes to twisted plugins.
This message from Ubuntu's Matthias Klose explains the issue and offers a solution:
啊，我尝试这样做但失败了。我认为这是可能的，具体取决于您想要针对哪个 Debian/Ubuntu 版本，以及您想要投入多少精力。
有两种方法：
twisted/plugins/中在扭曲的树中。这很痛苦，因为 Twisted 在不同版本中使用不同的方法进行打包（Lucid 中的python-support与 Natty IIRC 中的dh_python2），并且（粗略地说）您的包需要以与 Twisted 相同的方式打包就是为了使其工作。twisted/plugins/目录。然后，IIRC，问题就变成了创建的符号链接森林包含扭曲的目录（因为它不是一个包）。Argh, I've tried to do this and failed. I think it's possible depending on which Debian/Ubuntu releases you want to target, and how much effort you want to put in.
There are two approaches:
twisted/plugins/in the twisted tree. This is a pain because Twisted is packaged using different methods in different releases (python-supportin Lucid vsdh_python2in Natty IIRC) and (roughly speaking) your package needs to be packaged the same way as Twisted is to make this work.twisted/plugins/directory installed alongside your code. Then, IIRC, the problem becomes having the forest of symlinks that gets created include the twisted directory (as it's not a package).