atom feed23 messages in net.sourceforge.lists.plone-developersRe: [Plone-developers] QuickInstaller...
FromSent OnAttachments
Martin AspeliFeb 26, 2009 6:19 pm 
Hanno SchlichtingFeb 27, 2009 2:54 am 
Martin AspeliFeb 27, 2009 2:59 am 
Hanno SchlichtingFeb 27, 2009 3:25 am 
Martin AspeliFeb 27, 2009 3:47 am 
Matthew WilkesFeb 27, 2009 3:53 am 
Ricardo AlvesFeb 27, 2009 4:18 am 
Wichert AkkermanFeb 27, 2009 4:59 am 
Hanno SchlichtingFeb 27, 2009 5:09 am 
Martin AspeliFeb 27, 2009 5:29 am 
Daniel NouriFeb 27, 2009 5:35 am 
Chris RossiFeb 27, 2009 6:34 am 
Ricardo AlvesFeb 27, 2009 6:39 am 
Wichert AkkermanFeb 27, 2009 7:48 am 
Rob MillerFeb 27, 2009 11:25 am 
Maurits van ReesFeb 28, 2009 2:19 pm 
Hanno SchlichtingMar 14, 2009 8:22 am 
Lennart RegebroMar 14, 2009 8:42 am 
Hanno SchlichtingMar 14, 2009 9:06 am 
Gilles LenfantMar 14, 2009 11:33 am 
Martin AspeliMar 14, 2009 11:33 pm 
Wichert AkkermanMar 14, 2009 11:51 pm 
Alexander LimiMar 16, 2009 4:47 am 
Subject:Re: [Plone-developers] QuickInstaller kills local utilities upon product re-install
From:Hanno Schlichting (hann@hannosch.eu)
Date:Feb 27, 2009 3:25:38 am
List:net.sourceforge.lists.plone-developers

Martin Aspeli wrote:

Hanno Schlichting wrote:

Martin Aspeli wrote:

However, stomping on registrations and deleting data is bad, no matter what reasons that data was there in the first place.

What do you expect to happen if you ask someone to uninstall? It deletes data, that's its whole point. Reinstall means uninstall + install, you use it if you seriously screwed something and want to start from scratch.

Actually, I use it all the time during development, to get changes to my GS profile installed. I don't want to lose my persistent utility state just because of that.

Then you shouldn't reinstall your product. You want to go to portal_setup and reapply the profile. Developers know how to do this, no? The reinstall button in the control panel is for end users.

The re-install button is there now, and people use it all the time.

I consider removing the reinstall button and not encouraging its use a possible workaround.

I don't think we can do that in 3.x, which means that I still think my workaround is better than yours. ;-)

I think we can do this, as the current behavior of the button does not make any sense and leads to data loss in a number of situations. I consider the button in its current form to be a bug.

Another option may be to have the re-install button attempt no uninstall whatsoever, and just re-run the installation. I think people expect to have to "uninstall" and then "reinstall" if they really want to get back to ground zero. I bet most people expect "re-install" to indeed just install again.

Most people expect reinstall to upgrade. The wording of the message that comes with it is:

"This product has been upgraded. Filesystem version is 1.0. Reinstall: <reinstall button>"

It's entirely stupid. Just because the file system version changed, there is hardly ever a reason to reapply the configuration profile. And certainly not to uninstall the entire product, loose all your own configuration changes and start from scratch with the new defaults of the product.

In 90% of the cases a newer version of an add-on does not need a new configuration to be applied. The installation routines for add-ons hardly ever change. I think we are better of in most cases to not offer an upgrade message in the UI at the current stage and have people use the reinstall button in the ZMI or the portal_setup reapply method only if it is really needed.

Hanno

------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H