We cannot do distribute mercurial with web2py because it is GPL and it would not allow us to claim the commercial exception (redistribution of bundled binaries). I only incorporate third party BSD-like code in web2py.
Massimo On Dec 3, 1:00 pm, Yarko Tymciurak <resultsinsoftw...@gmail.com> wrote: > On Dec 3, 11:34 am, Jonathan Lundell <jlund...@pobox.com> wrote: > > > On Dec 3, 2009, at 9:28 AM, mdipierro wrote: > > > > why? We only need to check if the app version is less then the current > > > web2py version and eventually display a link that gives the admin the > > > option to install the latest version of the app. > > > > Are you thinking of something different? > > > Yes, I'm thinking of detecting whether the apps have been modified by the > > user. > > If we actually integrated hg use into web2py (the user would never > need to use it - just know it's there, and could if wanted) then this > would really become a smaller issue: for example, update an app > would become an hg merge, with a check / checkin of the current app > beforehand (with appropriate automatically generated comment: "Update > to web2py version xxx"). > > Conflicts would be handled as normal; rollback would be facilitated. > > This wheel is already invented - any reason to NOT use it? > > (just thinking out loud) > - Yarko > > > > > A reasonable default policy would be to automatically upgrade (on an app by > > app basis) apps that have not been modified since installation or the last > > upgrade. > > > > On Dec 3, 11:23 am, Jonathan Lundell <jlund...@pobox.com> wrote: > > >> On Dec 3, 2009, at 9:18 AM, mdipierro wrote: > > > >>> It could be even simpler like keep a copy of the VERSION file into > > >>> each of the basic apps. > > > >> What would be in the file? It'd have to be more than the version number > > >> and timestamp. > > > >>> On Dec 3, 11:12 am, Jonathan Lundell <jlund...@pobox.com> wrote: > > >>>> On Dec 3, 2009, at 9:06 AM, salingrosso wrote: > > > >>>>> We can make it a link of the side-bar that is alway there to remind us > > >>>>> that we have an option to upgrade apps if we have not done so. It > > >>>>> would be non-intrusive. The actual popup to point us to the link would > > >>>>> appear only once. > > > >>>>> I think this is the best solution. > > > >>>> If the standard apps had a supplementary signature file with, say, MD5 > > >>>> hashes of all the sources, we could detect whether there had been > > >>>> modifications and act accordingly. > > > >>>> Note also that the current scheme (--upgrade) is all or nothing, but > > >>>> it's not likely that a developer would be modifying all three of the > > >>>> standard apps. > > > >>>> (Me, I use my upgrade script that automatically snapshots the old > > >>>> version before overwriting it.) > > -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
