Packaging an app for distribution

[Oliver Lavery]

Hi,

The company I work for needed to add an infrastructure component to django for a site we're building. Since it could be generally useful we'd like to release it to the public in the not-too-distant future. We think it's pretty cool, and can't wait to share it with everyone; with the huge head start we got from django we're happy to give back in return. The details will have to wait until the code is actually available though.

In any event, I was wondering if anyone had any suggestions for how to package a (mostly) self-contained django app for distribution? We have a few settings, but otherwise it's merely an app that needs to live somewhere convenient. A patch against django.contrib is one option,  except that that path may reside in an .egg or might be linked to svn. Presently we simply have our app at the root of our site, but that could be a bit yucky for people who have their own site in a source control system (if you don't, you probably should).

Any ideas?

Tia,
~ol

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---