Re: [Plone-developers] ploneout - Or how using zc.buildout for a common Zope2 project might look like
On 1/18/07, Martijn Faassen <faassen@startifact.com> wrote: <snip>
Considering installation of Products we're in new territory anyway - they're not eggs, after all. I see in the result of ploneout that they get symlinked into the Products directory - will that work on Windows? <snip> * we can say something is a develop-Product. This means that you need a Product checkout that you refer to. This checkout is somehow linked so that Zope picks it up. (similar to the way develop-eggs has links to development packages). All entries in your bundle would be such a develop product.
'zope.conf' has a 'products' directive that you can use to point to other 'Products' directories other than the default in the INSTANCE_HOME. I believe you can add multiple 'products' directives to list multiple directories. Then you don't need to do any symlink or copying around. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
Sidnei da Silva wrote:
On 1/18/07, Martijn Faassen <faassen@startifact.com> wrote: <snip>
Considering installation of Products we're in new territory anyway - they're not eggs, after all. I see in the result of ploneout that they get symlinked into the Products directory - will that work on Windows? <snip> * we can say something is a develop-Product. This means that you need a Product checkout that you refer to. This checkout is somehow linked so that Zope picks it up. (similar to the way develop-eggs has links to development packages). All entries in your bundle would be such a develop product.
'zope.conf' has a 'products' directive that you can use to point to other 'Products' directories other than the default in the INSTANCE_HOME. I believe you can add multiple 'products' directives to list multiple directories. Then you don't need to do any symlink or copying around.
Great idea! We should try this. Hanno? :) I guess we can disregard most of my 'Products as eggs' mail and simply allowing us to point to products directories in the Zope 2 instance recipe. I think a good pattern would be to simply have a 'Products' directory directly in the buildout directory. Regards, Martijn
Martijn Faassen wrote:
Sidnei da Silva wrote:
On 1/18/07, Martijn Faassen <faassen@startifact.com> wrote: <snip>
Considering installation of Products we're in new territory anyway - they're not eggs, after all. I see in the result of ploneout that they get symlinked into the Products directory - will that work on Windows? <snip> * we can say something is a develop-Product. This means that you need a Product checkout that you refer to. This checkout is somehow linked so that Zope picks it up. (similar to the way develop-eggs has links to development packages). All entries in your bundle would be such a develop product.
'zope.conf' has a 'products' directive that you can use to point to other 'Products' directories other than the default in the INSTANCE_HOME. I believe you can add multiple 'products' directives to list multiple directories. Then you don't need to do any symlink or copying around.
Great idea! We should try this. Hanno? :)
Yep, we can try that one too. I thought I remembered people reporting bugs about the multiple Products directories at some point, but I cannot remember where that was exactly. I only did go for the symlink approach as that has been the way I did it on Windows, at the time I developed on Windows (see http://en.wikipedia.org/wiki/NTFS_junction_point for some explanation of Windows symlink support).
I guess we can disregard most of my 'Products as eggs' mail and simply allowing us to point to products directories in the Zope 2 instance recipe. I think a good pattern would be to simply have a 'Products' directory directly in the buildout directory.
Shouldn't we have the same distinction between products and development products as we have it with eggs and development eggs? If you develop a set of products based on CMF for example, you might want to have an unpacked tarball of the latest CMF release lying around and have it included in the Zope instance, plus your own products that probably come directly from a SVN checkout. This would give us both a products and develop-products directory, which you could both include in an instance's zope.conf. Hanno
Hanno Schlichting wrote:
Martijn Faassen wrote: [snip]
Great idea! We should try this. Hanno? :)
Yep, we can try that one too. I thought I remembered people reporting bugs about the multiple Products directories at some point, but I cannot remember where that was exactly. I only did go for the symlink approach as that has been the way I did it on Windows, at the time I developed on Windows (see http://en.wikipedia.org/wiki/NTFS_junction_point for some explanation of Windows symlink support).
I guess we can disregard most of my 'Products as eggs' mail and simply allowing us to point to products directories in the Zope 2 instance recipe. I think a good pattern would be to simply have a 'Products' directory directly in the buildout directory.
Shouldn't we have the same distinction between products and development products as we have it with eggs and development eggs?
Ideally perhaps, but since Products are just simple directories and don't really support this, we might want to skip this step for now.
If you develop a set of products based on CMF for example, you might want to have an unpacked tarball of the latest CMF release lying around and have it included in the Zope instance, plus your own products that probably come directly from a SVN checkout.
This would give us both a products and develop-products directory, which you could both include in an instance's zope.conf.
If we can make this work that would of course be nice. :) Regards, Martijn
participants (3)
-
Hanno Schlichting -
Martijn Faassen -
Sidnei da Silva