+1 the package could be web2py installation manager (a debconf launched by "dpkg --reconfigure web2py") and add dependencies like a system python and needed modules.
2010/10/14 mdipierro <mdipie...@cs.depaul.edu>: > the fact is... where is web2py going to reside? where are the apps > going to be? What will be the permissions? > Perhaps we should just provide a function like > > web2py deploy [where] > web2py start [where] > web2py stop [where] > web2py upgrade [where] > > which some other options like > --use apache > --use lighttpd > --use uwsgi > > and let the deploy function download the latest web2py. > > > On Oct 13, 4:17 pm, Richard <richar...@gmail.com> wrote: >> I remember talk about ability to upgrade through admin - is that >> practical? >> >> On Oct 14, 7:29 am, mdipierro <mdipie...@cs.depaul.edu> wrote: >> >> > I feel this will be a maintenance nightmare unless it somehow upgrades >> > itself. The release process of debian is very slow compared to ours. >> >> > On Oct 13, 3:12 pm, Michele Comitini <michele.comit...@gmail.com> >> > wrote: >> >> > > Hi José, >> >> > > The .deb is badly needed to spread web2py even more! >> >> > > Would that be useful for ubuntu also which is probaly the most common >> > > linux distro? >> >> > > The packaging must also take into account that a machine could have >> > > different instances of web2py. >> > > It would be a good idea to have some tools in the .deb to support the >> > > creation of different instances, maybe >> > > throughhttp://pypi.python.org/pypi/virtualenvsothatupgrade of >> > > system python doesn't break everything as it usually happens on >> > > debian with other python frameworks. >> >> > > mic >> >> > > 2010/10/13 José L. <jredr...@gmail.com>: >> >> > > > Hi, as it seems that time goes by, and no available packages for >> > > > Debian are ready, I'm going to begin to work on it seriously to upload >> > > > web2py to Debian. >> > > > I know >> > > > (http://groups.google.com/group/web2py/browse_thread/thread/45ea4327d7... >> > > > ) Mark told he was going to work on it, but I think that I have been >> > > > patient enough waiting since April. It's not only Debian is one of the >> > > > most important Linux distribution, also many other distributions as >> > > > Ubuntu are derivatives from Debian, so uploading web2py to Debian will >> > > > bring it to many users in the Linux world. >> >> > > > I'd like to have a package similar to the django one. There is a >> > > > python-django package, and I'd like to make a python-web2py package to >> > > > work in a similar way, so people don't need to relearn a new method of >> > > > work. >> > > > I'd like it to work as similar as possible to >> > > >http://codeghar.wordpress.com/2007/12/01/django-in-ubuntu/. >> >> > > > So, the main question for me is: >> > > > once gluon is installed in the PYTHONPATH and web2py.py installed in / >> > > > usr/bin, I would like to be able to tell the user: >> > > > execute python web2py.py in any directory and point your browser to >> > > >http://localhost:8000tobeginto work. >> >> > > > But, as web2py structure is today, I don't know if such thing is >> > > > possible (after adding every needed file to every needed path). >> >> > > > If not, what other approaches might be used to make any user in the >> > > > system able to use a system with a installed web2py structure? >> >> > > > On the other hand, if more people want to collaborate in the packaging >> > > > I'll be glad to open a project in alioth.debian.org, so we can work >> > > > together. >> >> > > > Regards. >> > > > José L. >> >>
