<div class="gmail_quote">Jonas,<br><br>On Mon, Aug 31, 2009 at 15:29, Luke Faraone <span dir="ltr"><luke@faraone.cc></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><div></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Why set DEB_PYTHON_MODULE_PACKAGES - I believe that should be autodetected if using proper package names. Even if not, I still suspect that you should rename the package to include a leading "python-" to not violate Python Policy.<br>
</blockquote></div><div><br>How about this: I'll split it off into three packages: <span class="il">rainbow</span>, python-<span class="il">rainbow</span>, and libnss-rainbow2. <br><br>python-* packages shouldn't install anything into /usr/sbin/ or /usr/bin as far as I can tell, so just renaming <span class="il">rainbow</span> to python-<span class="il">rainbow</span> would not be acceptable.<br>
<br>If that's acceptable to you, I'll make the changes. As it is, I think we're fine with just <span class="il">rainbow</span> and libnss-<span class="il">rainbow</span>.</div></blockquote></div><br>I didn't get a reply on this, maybe I missed it?<br>
<br>Should I have a separate python package for the rainbow python module and the binaries, or can I just keep them all in "rainbow"?<br><br clear="all"><br>-- <br>Luke Faraone<br><a href="http://luke.faraone.cc">http://luke.faraone.cc</a><br>