Hello, in order to do the packaging of web2py, I've done these things: - moved gluon to be a standard library of the system, integrated in the PYTHONPATH - moved : applications deposit logs site-packages VERSION web2py.py welcome.w2p to /usr/share/web2py -add created a web2py launcher at /usr/bin/
this web2py launcher is available at http://paste.debian.net/105739/ I've tried to keep: - the normal behaviour of web2py, - fulfill the FHS - respect the user changes in his permissions land - when a new version of the web2py package is installed the admin and welcome application are upgraded to the user (gluon and all the stuff at /usr/share/web2py are upgraded), but the upgrading doesn't disturb other applications the user has created in his userland, or the admin configurations the user has done. I'd like to know your opinion about these steps, specially if the web2py launcher is clean or it can raise any problem in the future. Also, when launcher starts from the Desktop menu, it should ask always for the port and password admin, and then launch the web browser. As gluon.widget.start(cron=True) begins the server loop, I'd like to know any idea about how to launch an external process (the web browser), after it has started. Regards. José L.
