Hi Yarko,
On Dec 10, 3:20 am, "Yarko Tymciurak" <[email protected]> wrote: > applications/modules/t2/rev12345 > > and a way for migrating modules - that is, only keeping around [1] newest > version, and [2] legacy versions that apps still used (but provide a way to > migrate). I can think of a couple of schemes for accomplishing this, none > of them "great". > > What would this (modules part) do? It would allow people to distribute > modules, and people running websites (e.g. clients) a recoverable way to > upgrade. It would also eliminate copies & copies of modules in every > application (e.g. like shared libraries). Yes, this sounds like a very good idea. It would help people share modules, and share applications with their associated modules, without breaking existing apps on the web2py server. It does introduce the added overhead of changing all your "import" statements every time you modify your module, however. --Jonathan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
