Christoph Haas wrote: > I could imagine a tool like "pylons-buildpackage" which creates a Pylons > application and makes a proper Debian package of it that can be > apt-installed. I'm eager to hear other people's ideas on that.
FWIW, I think such an installer should package up all the libraries in one Debian package, I imagine laid out something like: /usr/lib/some-pylons-app/lib/python/(bunch of eggs) Installing something in /usr/bin/some-pylons-app that sets up sys.path. This is similar to workingenv, but would be slightly different; you can pretty much manage it with setuptools options, plus a modified script. If there are libraries packaged already as Debian packages, you'd probably want to use the Debian package version. But I don't think it's worth making separate packages for each library unless many applications use that library, and the library is stable enough that conflicts are unlikely. Mako, for instance, would not be a good candidate. > I'm also interested in how other Debian users deploy Pylons applications. > Do you just copy the project directory onto another computer? Or do you > deploy into /usr/local? Or am I the only one using Debian here? :) I use workingenv and a workingenv requirements file, and some shell scripts to do the setup from there. -- Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
