[Zope-CMF] Re: [dev] GenericSetup: using global steps
Tres Seaver wrote: Worse, an import is potentially destructive. I am now of the opinion that content import / export should be treated as a separate application, not built into the profile. From a design perspective, I'd tend to agree. I've always felt that the 'structure' import step sat a bit awkwardly with the rest of GS. That said, there are grey bits. For example, I'm working on a Plone enhancement to make it possible to manage portlet setup (assignment) via GenericSetup. That's easy enough for "global" portlets, but some portlets may be assigned to specific folders. Both export and import are tricky here. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] Re: [dev] GenericSetup: using global steps
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 yuppie wrote: > yuppie wrote: >> GenericSetup trunk has global step registries. I propose to use the new >> ZCML directive for registering all GenericSetup and CMF import and >> export steps globally. And to remove the import_steps.xml and >> export_steps.xml files from the profiles shipped with CMF. >> >> This also requires to add a flag file for the 'various' step. >> >> I already started implementing this. If there are no objections, I'll >> soon check in my changes. > > Done. > > Not sure what to do with the 'content' steps: The 'content' export step > is the only one I would not like to run by default. A content snapshot > might be quite expensive. Worse, an import is potentially destructive. I am now of the opinion that content import / export should be treated as a separate application, not built into the profile. > For now the 'content' steps still must be registered locally or in > custom ZCML. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHbVLF+gerLs4ltQ4RAqKWAKCUD/EcpzrssBj+16aOELEdr6ECbACgvDtV Qcus85UPVTKl9aZ1mPmASDw= =5p1T -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] Re: [dev] GenericSetup: using global steps
yuppie wrote: GenericSetup trunk has global step registries. I propose to use the new ZCML directive for registering all GenericSetup and CMF import and export steps globally. And to remove the import_steps.xml and export_steps.xml files from the profiles shipped with CMF. This also requires to add a flag file for the 'various' step. I already started implementing this. If there are no objections, I'll soon check in my changes. Done. Not sure what to do with the 'content' steps: The 'content' export step is the only one I would not like to run by default. A content snapshot might be quite expensive. For now the 'content' steps still must be registered locally or in custom ZCML. Yuppie ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] CMF Tests: 11 OK
Summary of messages to the cmf-tests list. Period Fri Dec 21 12:00:00 2007 UTC to Sat Dec 22 12:00:00 2007 UTC. There were 11 messages: 11 from CMF Unit Tests. Tests passed OK --- Subject: OK : CMF-1.5 Zope-2.7 Python-2.3.6 : Linux From: CMF Unit Tests Date: Fri Dec 21 21:33:29 EST 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-December/007377.html Subject: OK : CMF-1.5 Zope-2.8 Python-2.3.6 : Linux From: CMF Unit Tests Date: Fri Dec 21 21:35:00 EST 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-December/007378.html Subject: OK : CMF-1.5 Zope-2.9 Python-2.4.4 : Linux From: CMF Unit Tests Date: Fri Dec 21 21:36:31 EST 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-December/007379.html Subject: OK : CMF-1.6 Zope-2.8 Python-2.3.6 : Linux From: CMF Unit Tests Date: Fri Dec 21 21:38:01 EST 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-December/007380.html Subject: OK : CMF-1.6 Zope-2.9 Python-2.4.4 : Linux From: CMF Unit Tests Date: Fri Dec 21 21:39:31 EST 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-December/007381.html Subject: OK : CMF-2.0 Zope-2.9 Python-2.4.4 : Linux From: CMF Unit Tests Date: Fri Dec 21 21:41:01 EST 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-December/007382.html Subject: OK : CMF-2.0 Zope-2.10 Python-2.4.4 : Linux From: CMF Unit Tests Date: Fri Dec 21 21:42:31 EST 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-December/007383.html Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.4 : Linux From: CMF Unit Tests Date: Fri Dec 21 21:44:01 EST 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-December/007384.html Subject: OK : CMF-2.1 Zope-trunk Python-2.4.4 : Linux From: CMF Unit Tests Date: Fri Dec 21 21:45:31 EST 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-December/007385.html Subject: OK : CMF-trunk Zope-2.10 Python-2.4.4 : Linux From: CMF Unit Tests Date: Fri Dec 21 21:47:01 EST 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-December/007386.html Subject: OK : CMF-trunk Zope-trunk Python-2.4.4 : Linux From: CMF Unit Tests Date: Fri Dec 21 21:48:32 EST 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-December/007387.html ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
