[Python-modules-team] When to split up packages?

Michael Fladischer michael at fladi.at
Thu Apr 29 10:49:36 UTC 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I plan on packaging django-storages[1], a collection of storage backends
for Django. Upstream currently includes one Python package with 10
modules, each representing a backend, most of them having dependencies
on other python packages (like python-couchdb, python-boto, ...).

What would be the best approach to get this packaged for Debian? Create
one package with all the backend modules in it and simply pull in all
dependencies?
Or create a single package for each backend with only the specific
dependencies on each of them? This sounds like overkill to me but I'm
not sure.

What do you think?

  [1] http://code.welldev.org/django-storages/wiki/Home
- -- 
Michael Fladischer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkvZZEAACgkQeJ3z1zFMUGY6QACfWA1pm8Aw3aeCaGfk3dXn4SY7
nZ4AnjQ+F/zSeWg/jXNDYDUKzh/yMWw2
=ki3d
-----END PGP SIGNATURE-----




More information about the Python-modules-team mailing list