[Python-apps-team] Packaging When I'm the "Upstream"

[Bernd Zeimetz]

Hi,

> These tutorials usually begin by having you download some tarball that
> is already available via the Web.  If possible, I'd like to avoid
> packaging up my software in a tarball, just to produce a Debian package.
> I'd like to keep my "debian" packaging directory in the same repository
> that holds my "upstream source", if it's not going to complicate things
> too much.

Please don't put the debian directory in your tarball. It is much more
easy to handle a package if the debian directory is only shipped in the
.diff.gz, as you don;t have to mess with 'your' source if there's
something to change when you're not available (think on a security bug
detected while you're on vacation). Much more easy to add a proper
proper patch in such cases if you don't have to upload the full tar.gz,
but only a new diff.gz.


>   * Should I just create an "upstream tarball" and, from there, create
>     a package in one of the traditional ways?

yes.

>   * How to go about web server configuration?  I.e., it'd be nice to 
>     walk the user through some kind of "wizard", at installation 
>     time, asking him what domain/path he'd like to serve the app from.

Have a look into debconf

>   * How to go about database creation and initialization?  Is it okay to
>     make this a post-install process, that the user is questioned about
>     the first time he "visits" the app.

Take a look into the dbconfig-common package.


> I'm not subscribed to this mailing list, at this time, so please include
> my address in any reply.

Done.


If you work on a python related application, you could join the PAPT[1],
also visiting us in #debian-python on the OFTC network is a good way to
get questions answered fast or to find a sponsor for your package.

Much information about how to create a package are available on [2]. For
examples you can also look at the source of similar packages.

[1] http://python-apps.alioth.debian.org/policy.html
[2] http://www.debian.org/doc/devel-manuals


Hope that helps,

Bernd
-- 
Bernd Zeimetz
<bernd at bzed.de>                         <http://bzed.de/>