Hi Christoph, I use Debian and the way I deploy my apps is using a virtual Python installation into a user account I setup for each app. I usually then just checkout the latest source code and run:
~/bin/python setup.py develop The problem with trying to package up a Pylons app into a Debian package is that you have to worry about all the dependencies. You could package up all the dependencies too but that would be a pain. I suppose the alternative solution if you really want to use a Debian package is to setup workingenv and then make a package out of the entire workingenv directory with the dependencies included as part of the one package. I've always been happy to stick to using easy_install and eggs myself but when packages have C extensions the benefits of creating .debs become more apparent. Also it is useful to have different packages available to different Pylons apps and if you just use .debs to install software into the main Python directories you can't do that. I'd be interested to hear if you come up with a good solution though? Cheers, James Christoph Haas wrote: > Dear list, > > I'm spending some of my spare time as a Debian developer which means > creating Debian (binary) packages from software. In Debian you don't use > easy_install to install Python modules but rely on packages that the > distribution provides. E.g. to install Pylons and all it's dependencies > you issue an "aptitude install python-pylons" which means that certain > other packages are installed automatically: > > python > python-routes > python-myghty > python-paste > python-pastedeploy > python-pastescript > python-formencode > python-simplejson > python-webhelpers > python-nose > python-beaker > > Naturally I wondered how to properly deploy a self-made Pylons application > on Debian. Perhaps someone with more insight of the Paster deployment > process can help understand what's going on and whether that can be > scripted to make it a Debian package. Or perhaps other readers who are > familiar with Debian package have an idea, too? > > 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. > > For those not being involved into Debian package management: a Debian > package takes the (upstream) software itself (usually a > software-1.0.tar.gz file) and adds a special "debian/" subdirectory that > contains control information on the page. Such information deals with > copyright, what other packages are needed (as stated above), which files > are to be put where in the file system and a Makefile/shell script that is > run to "make" the software (like "./configure; make; make install"). > > 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? :) > > Kindly > 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 -~----------~----~----~----~------~----~------~--~---
