I'd suggest starting with the combination of Evan's zopemake and zctl scripts. One thing that zopemake could be extended with is an autoconf-style "configure" that figures out where the appropriate version of Python is, which C compiler to use, etc.
- C ----- Original Message ----- From: "Paul Everitt" <[EMAIL PROTECTED]> To: "Behrens Matt - Grand Rapids" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Friday, March 01, 2002 7:53 AM Subject: Re: [Zope-dev] Zope 2.6 planning - call for contributors! > > +1, and I say that knowing that it means I have to help. I'm willing to > write the docs for whoever works on the code. > > A gentle reminder on some of the posts in this thread. Please don't > respond with "I'd really like <some good idea>." Respond with "I'm > willing to do the work for <some good idea>." That's part of the point > with Brian's note. > > You don't _have_ to do the code work. If you write up the docs for > <some good idea>, you've likely done most of the work. > > --Paul > > Behrens Matt - Grand Rapids wrote: > > Brian Lloyd wrote: > > > > > Let's get a discussion > > > >> started to define 2.6. > > > > > > This isn't exciting by any means unless you're one of the people who > > package Zope up for distribution, or maybe you're one of the people who > > manage lots of little Zopes on one system; but I'd like to revive the > > "grand unified Zope installation and control" proposal that has been > > floated by many people (including me) in one form or another for some > > time. Wikiwise, this would wrap up > > http://dev.zope.org/Wikis/DevSite/Proposals/ZopeStartupProvisions and > > http://dev.zope.org/Wikis/DevSite/Proposals/InstallationAndConfiguration, > > at least. > > > > To summarize, this would involve > > > > - an expanded build program with an installation scheme that would allow > > multiple versions of Zope to be present on the same system > > > > - making that installation 'secure by default' > > > > - a registry of Zope installations and one of instances and their > > configuration settings > > > > - a 'zopectl' program or similar that would be able to start and stop > > instances > > > > - a 'zopeinstance' program or similar that would become the > > _recommended_ way of setting up Zope, by creating an INSTANCE_HOME > > > > It would be nice if > > > > - the same framework could apply to Zope 3, maybe taking care of that > > piece ahead of time > > > > I'm more than willing to head this up, though I question how long we > > have before 2.6 to do so. > > > > _______________________________________________ > > Zope-Dev maillist - [EMAIL PROTECTED] > > http://lists.zope.org/mailman/listinfo/zope-dev > > ** No cross posts or HTML encoding! ** > > (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce > > http://lists.zope.org/mailman/listinfo/zope ) > > > > > _______________________________________________ > Zope-Dev maillist - [EMAIL PROTECTED] > http://lists.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > http://lists.zope.org/mailman/listinfo/zope-announce > http://lists.zope.org/mailman/listinfo/zope ) > _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
