On Monday 05 March 2007 22:29, Ian Bicking wrote: > 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)
I don't believe it would make things easier. All components like python-sqlalchemy, python-mako, python-webhelpers or python-pylons are already packaged for Debian. If by "all the libraries" you mean these packages it would create a second installation of them on a system which is not desirable. It would be best if the Pylons user who is about to create a Debian package sets up the proper (Debian-)dependencies in the debian/control file so just the Pylons project itself needs to be packaged. > I use workingenv and a workingenv requirements file, and some shell > scripts to do the setup from there. I haven't worked with workingenv yet. Is it feasable to ship an application with all the needed dependencies into such a "chroot" and run them on a production system? Christoph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
