Hi Christian,I've looked a bit at zopeproject, but I'm still wondering if
it's possible to still install
zope as eggs without zopeproject (if that even makes sense). Will
become _the_ way of developing in the future? Because I don't see a reason
using a tarball install when you can't smoothly install those nice zope
(e.g lovely.tag) that depend on the eggversion of zope.
I have a hosting situation that is a bit unclear
when it comes to running zopeproject because they use good old instances.
I have a discussion with them at the moment so I hope I get this sorted out
On 10/31/07, Christian Klinger <[EMAIL PROTECTED]> wrote:
> do you know zopeproject
> with the help of zopeproject you will get
> a buildout where you can specifiy further
> dependencies in your application.
> > Good afternoon list,
> > I currently have a Zope 3.3.1 installation (tarball) and have written
> > some code that uses zc.catalog
> > and hurry.query. These two were installed as eggs and work fine (I used
> > zc.catalog 1.1 because
> > later versions required a lot of zope eggs)
> > I'd like to use more packages but I see that most of the new stuff today
> > require eggs from the
> > 'eggified' version of Zope..
> > So I figure I just might as well switch to all eggs and join the future.
> > I want this to go as smooth as
> > possible. Not sure how to get started though.
> > 1. Which package to easy_install to get Zope 3? And when you've got it
> > installed can you say that
> > you actually run a certain version of Zope any longer?
> > 2. If I install everything as eggs, how do I actually create, configure
> > and run instances? Or do I
> > actually keep my old 3.3.1 install alongside the new eggs?
> > 3. Any other suggestions?
> > Greatly appreciate any answers bringing some clarity to this
> > Regards
> > Jesper
Zope3-users mailing list