Martin Aspeli wrote: > Hanno Schlichting wrote: > >> I haven't read all the mails in detail, but I have the feeling we are >> duplicating lots of effort here. >> >> Rob and Tres did some great work on GenericSetup which is available from >> a branch of GS right now: >> svn://svn.zope.org/repos/main/GenericSetup/branches/tseaver-bbq_sprint > > Ah, interesting! > > Any idea when third party products may expect to be able to depend on this?
It is planned to go into GS 1.3 which may land be used with CMF 2.1 - thus Plone 3.0, but I guess Rob wouldn't mind any help actually finishing it in time ;) >> While Rob can explain this in more detail I guess, here's a short >> version from the CHANGES.txt: >> >> - Profiles now support version numbers; setup tool tracks profile >> versions during upgrades. >> >> - Added support for nested 'upgradeStep' directives; expanded upgrade >> step registry into a real registry object and not just a dictionary. >> >> - Added support for 'metadata.xml' in the profile (read during profile >> registration) to register profile description, version and dependencies. >> >> - Merged CPS's upgradeStep ZCML directive, w/ corresponding tool support. >> >> I think most of the things discussed in this thread are to some extent >> already built into that GS branch. > > Sounds great. ;) > >> On the Plone integration side I would want to tweak QuickInstaller and >> the add-on products control panel a bit so that in the end once a >> product is installed and a new version is available an upgrade button >> for the product is available. As we already store the currently >> installed version number in the QuickInstaller tool we can do that even >> for older products where the version numbers are not yet stored in the >> portal_setup tool. > > Yes, this is probably the most natural UI. I also see a need for a > "force upgrade from version X" as we have in portal_migration. The portal_setup tool has a ZMI screen that lists all available upgrade steps and lets you run any of them, as far as I have seen. That should be good enough for the integrator whereas the simple interface in the control panel should be sufficient for the end user. If you need a different UI there's an API you can built upon... Hanno _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
