On Mar 3, 11:48 am, Dragonfyre13 <dragonfyr...@gmail.com> wrote: > If it's untarred over the top of the old one, any files that are not > in the new tar file will be left there. Since an app is supposed to > kind of be self contained, shouldn't it remove the old app, and then > untar to the directory?
A trivially simple way to handle this would be to have the concept of an application "trash can", where a current app would be moved to "trash", and a new one installed. Another way would be to literally have app-area per-application repositories (hg), and literall just "pull" the new app (including any file deletions) - but this would mean the tar / w2p file format giving way to /letting mercurial manage updates in these circumstances (which would probably not be bad). - Yarko > > On Feb 16, 11:08 am, Jonathan Lundell <jlund...@pobox.com> wrote: > > > On Feb 16, 2010, at 8:32 AM, DenesL wrote: > > > > Thanks (it is copy/paste of the original). > > > Do you know of any docs on usage?. > > > On the admin app's app-installation page, there's a checkbox to enable > > overwriting of an uploaded app. If not checked, the behavior is the same as > > before: an attempt to install an app with the same name as an installed app > > fails. In the overwrite case, the new app simply gets untarred over the old > > app. > > > > On Feb 16, 11:21 am, Jonathan Lundell <jlund...@pobox.com> wrote: > > >> On Feb 16, 2010, at 7:16 AM, DenesL wrote: > > > >>> New features not documented in Book (2nd edition) > > > >>> 1.75.2 > > >>> - no more cron with -S option > > >>> - ability to override/upgrade and app > > > >> overwrite > > -- 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.
