The debian packaging group is online:
http://alioth.debian.org/projects/pkg-web2py/
Please, join the group if you want to collaborate/help/test the
packaging.
I'll wait some days before beginning to upload the first files.
Also, all the packaging talk can be done in the group, instead of
floodin
On 16 oct, 15:40, LightDot wrote:
> I have written an internal Fedora RPM for web2py a while ago and tried
> to follow Fedora's packaging guidelines. I'm a RHEL/CentOS sysadmin
> and take care of quite a few hosting servers, my main objective was to
> easily use it on our RHEL/CentOS servers wit
Thanks this is a helpful comment. I will ty to answer some questions
although I do not have an answer.
On Oct 16, 8:40 am, LightDot wrote:
> I have written an internal Fedora RPM for web2py a while ago and tried
> to follow Fedora's packaging guidelines. I'm a RHEL/CentOS sysadmin
> and take care
I have written an internal Fedora RPM for web2py a while ago and tried
to follow Fedora's packaging guidelines. I'm a RHEL/CentOS sysadmin
and take care of quite a few hosting servers, my main objective was to
easily use it on our RHEL/CentOS servers with Cherokee.
I don't want to "steal" the Debi
On 16 oct, 10:54, Mark Breedveld wrote:
> >> apache2-web2py
>
> Well I originally launched the same plan as you and we also came too
> the same conclusion as you. No way too do it, because of the three
> reasons I mentioned before.
> guidelines, maintainable, etc
>
> So stick to the original pla
On 16 oct, 09:59, Mark Breedveld wrote:
> Some packager told as that libraries should be in some directory
> according too the guidelines. I checked it back then and he was right.
> But I don't now how heavy that counts.
>
It's a must: http://www.debian.org/doc/packaging-manuals/python-policy/
>> apache2-web2py
Well I originally launched the same plan as you and we also came too
the same conclusion as you. No way too do it, because of the three
reasons I mentioned before.
guidelines, maintainable, etc
So stick to the original plan. Get a simple version of web2py on air.
With documentati
Some packager told as that libraries should be in some directory
according too the guidelines. I checked it back then and he was right.
But I don't now how heavy that counts.
It would also be easier to update several instances of web2py since
the most updates will happen there.
But if you say you
I do not know what the best way and retaining the ability to to hot
upgrades is important. Just to add a piece of information. Jonathan is
working on a re factoring that will allow web2py to be installed in
one folder, keep applications/configurations/logs in another, and run
from a third folder. T
IMHO I would not separate anything. A big part of Web2py's magic is
that you do don't need to "install" it. Keeping everything together
insures that upgrades will always work via the web2py web interface
(with a pleasant side effect being that you do not have to repackage
each time Web2py is update
On 15 oct, 13:32, Mark Breedveld wrote:
> You have the idea. Thanks for clearing it towards the others.
>
> My guesses it we need to do both.
> Because Jose goal is general purpose and mine aswell,
> but comes with overkill in the most cases.
>
> In Jose case I would suggest a slight change.
> w
On 15 oct, 11:33, Jurgis Pralgauskis
wrote:
> Maybe You could usehttps://help.launchpad.net/Packaging/SourceBuilds/
>
> if you'd create stable branch on bazar and add packaging recipy
> likehttps://code.edge.launchpad.net/~mdipierro/web2py/devel/+new-recipe
> fromhttps://code.edge.launchpad.net
On 14 oct, 23:51, Christopher Steel wrote:
> If your break things down into one or more “debian” packages and at
> least one web2py application you could end up with a phenomenally
> powerful and easy to maintain setup that could have resounding
> repercussions, so to speak, for all parties.
>
>
You have the idea. Thanks for clearing it towards the others.
My guesses it we need to do both.
Because Jose goal is general purpose and mine aswell,
but comes with overkill in the most cases.
In Jose case I would suggest a slight change.
web2py-core
web2py-gluon
This has been discusses before,
Maybe You could use
https://help.launchpad.net/Packaging/SourceBuilds/
if you'd create stable branch on bazar and add packaging recipy like
https://code.edge.launchpad.net/~mdipierro/web2py/devel/+new-recipe
from
https://code.edge.launchpad.net/~mdipierro/web2py/devel (notice
code.EDGE.launch...)
If your break things down into one or more “debian” packages and at
least one web2py application you could end up with a phenomenally
powerful and easy to maintain setup that could have resounding
repercussions, so to speak, for all parties.
How does the following example sound?
Package 1, web2py
Well that makes a hope clear.
I learned a lot from your explanation.
You did rule out almost the obstacles.
And the last one should solve able.
Changing some process within web2py.
I need this for my project.
So if you need anything, please let me know.
Direct mail will grantee answer...
and all
On 14 oct, 17:24, Mark Breedveld wrote:
> I've not so much time.
> But we have done this discussion before.
> There where three problems with packaging web2py.
>
> - Really frequent release period (not impossible for someone with a
> lot time)
I've already answer this before: Debian sid for fre
I've not so much time.
But we have done this discussion before.
There where three problems with packaging web2py.
- Really frequent release period (not impossible for someone with a
lot time)
- Difficult to implement according the packaging guidelines
- Difficult to implement with user separation
On 14 oct, 02:36, Mark Breedveld wrote:
> Hello Guys,
>
> My apologise for my late update on the project.
> Had to get my propedeuse :p.
>
> And next 1 - 1,5 year I hope to do my graduation project on HRO.
> Which I hope is implement or extends web2py manager.
>
> In other topics we discussed t
On 13 oct, 23:18, Tim Michelsen 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.
>
> You can have automatic daily builds of a source tree import to your
> PPA:https://help.launchpad.net/Pac
On 13 oct, 23:17, Richard wrote:
> I remember talk about ability to upgrade through admin - is that
> practical?
>
It works, but it must be disabled in the Debian package. Versions can
not be upgraded without upgrading the package, that would break the
system packages database. As an example,
On 13 oct, 22:29, mdipierro 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.
>
Yes and not. Debian is three distributions: stable, testing and sid.
If you want to run sid, you have the most upg
Hello Guys,
My apologise for my late update on the project.
Had to get my propedeuse :p.
And next 1 - 1,5 year I hope to do my graduation project on HRO.
Which I hope is implement or extends web2py manager.
In other topics we discussed the complexity and problems.
Some of us agreed that we woul
On 13 oct, 18:17, Richard wrote:
> I remember talk about ability to upgrade through admin - is that
> practical?
>
In production with wsgi-apache2 is not practical.
A dream if I can do in the server: sudo apt-get update, sudo apt-get
upgrade.
The process of debian is very slow, perhaps a ppa. An
+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 :
> the fact is... where is web2py going to reside? where are the apps
> going to be? What will be the permi
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 light
> I feel this will be a maintenance nightmare unless it somehow upgrades
> itself. The release process of debian is very slow compared to ours.
You can have automatic daily builds of a source tree import to your PPA:
https://help.launchpad.net/Packaging/SourceBuilds/Recipes
I remember talk about ability to upgrade through admin - is that
practical?
On Oct 14, 7:29 am, mdipierro 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 Comitin
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
wrote:
> Hi José,
>
> The .deb is badly needed to spread web2py even more!
>
> Would that be useful for ubuntu also whic
On 13 oct, 21:00, mdipierro wrote:
> web2py -f folder
>
> It should work but you may want to check. Perhaps we may need a patch.
I'll try it,
I guess some other files will be needed, but I'll report my progress.
Anyway maybe you could add some code to web2py.py so if it doesn't
find the glu
web2py -f folder
It should work but you may want to check. Perhaps we may need a patch.
Massimo
On Oct 13, 1:55 pm, José L. wrote:
> 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
32 matches
Mail list logo
