My excuses, that was not what I ment. I ment was.
How do you package the application before publish it? Is there a repo? Do have a script to do that? It is a question about the process, not a technical web2py question. And my second question was how should we develop the deb package? Is there a repo that we could use for package code/script? Who approves or creates the debian packages for every release? And how should we use it? I'm new to the opensource, so any advice would be welcome. regards Mark, On Apr 20, 4:09 pm, mdipierro <[email protected]> wrote: > This is partially true. I approves changes in the web2py source code > but I am not convinced that packaging fordebianrequires changing in > the web2py source code. In fact, I hope it does not. If it does not, > there is nothing for me to approve, although I will be happy to review > your proposal and test it. > > Thanks for your help on this. > > Massimo > > On Apr 20, 3:15 am, Mark Breedveld <[email protected]> wrote: > > > Hello Massimo, > > > I'm almost done with my exames, so i've a little sparetime left. > > What brings me back to webpy packaging. > > > Well I'm fairly new to web2p development. > > And have no clue how the process goes. > > > I read somewhere in the mailinglist that you approve changes. > > And publish them into a new version. > > > My question is: > > How and where would you like to have the web2py packaging system > > developt? > > and > > How would you like to have the packaging system to work? > > > Because if the above statement is right, then you would be the end > > user of the packaging system. > > > I hope you can get me on the road. > > > regards, > > > Mark Breedveld, > > > -- > > Subscription settings:http://groups.google.com/group/web2py/subscribe?hl=en
