2011/4/27 Jonas Smedegaard <span dir="ltr"><<a href="mailto:dr@jones.dk">dr@jones.dk</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
But start with releasing upstream code independent from Debian<br>
packaging.<br></blockquote><div><br>Hmm, I think you misunderstand. The code is released. It is a single .py file.<br><br>We've gone to significant effort to make sure this single .py has everything people need to use the program as a stand-alone tool. It even generates its own configuration files. :-)<br>
<br>Now we would like to offer pagekite as a
debian package in order to make systems integration easier (running
pagekite.py as an always-on background service for example), make
upgrades automatic, all that good stuff.<br>
<br>There's a general assumption that a "release" is an archive consisting of multiple files, including an installer which copies binaries and libraries to the right place (like python's distutils). We kept things so simple we didn't feel we needed that, but my question was whether it would make packaging simpler (integrate better with the Debian toolchain) if we created (for example) a minimal .tar.gz including a distutils setup.py first.<br>
<br></div></div>-- <br>Bjarni R. Einarsson<br>The Beanstalks Project ehf.<br><br>Making personal web-pages fly: <a href="http://pagekite.net/" target="_blank">http://pagekite.net/</a><br>