Wow, lengthy discussion, let me sum up some of my thoughts:

1) I already have Ubuntu packages in a private PPA. I'll clean those
up and make public if there is such interest.

2) Jason, if you know a DD, it'd be great to ask for mentorship. I
have packaged python deb stuff before (I'm a Maemo contributor), it's
just that none of that was official Debian business.

3) It would not get out of date. Every distribution has an updates
repository that is *expected* to be update with newer ABI/API
compatible versions of the initial release. Since web2py has backward
compatibility as one of it's cornerstones, this means we can have up-
to-date versions in even fairly old distribution releases.

4) Not sure how much use from having .deb-s directly on the web2py.com
page (think dependencies, etc). Pointing to a repository is the Right
Way (TM).

5) Debian repositories are not just for PR. web2py is easy to install,
but that doesn't mean it looks nice or professional on a .deb based
system. Think about automatic service startups, interfacing with with
apache, having libraries in the right place, satisfying various python
dependencies, an OS friendly/consistent way of upgrading/installing,
being backup friendly, etc.

On May 29, 3:43 am, mdipierro <[email protected]> wrote:
> > Presently Web2Py so easy to install, even a Cave Man could do it?  :-)
>
> I agree. This is for politics and public relations, not convenience.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py Web Framework" 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/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to