Shane Hathaway wrote:
I've created a patch that allows you to create redistributable archives
with the distribution tab. It's checked in to CVS on a branch. This
is what was needed for us to start using the distribution tab more
frequently.
Great :-)
Thanks again Shane...
Is the patch
Chris Withers wrote:
Dieter Maurer wrote:
What is needed is a new way of installing Zope stuff for the following
categories:
1. Python Base Products (Like ZPatterns, PTKBase and TrackerBase)
2. Instantiatable Products (like TinyTables, Squishdot and Tracker)
3. Interface
Bill Anderson wrote:
I believe he is talkin gabout the __init__ function checking to see if
the .zexp has been imported, and if not, importing it for you. It's an
idea I have kicked around, but haven't tried yet.
IIRC, the 'Distribution' tab creates all this for you...
It creates a binary
Dieter Maurer wrote:
What is needed is a new way of installing Zope stuff for the following
categories:
1. Python Base Products (Like ZPatterns, PTKBase and TrackerBase)
2. Instantiatable Products (like TinyTables, Squishdot and Tracker)
3. Interface Skins (none right now,
Here is a page by Butch Landingin at
http://www.zope.org/Members/butchland/ZopePackProposal
He talks about the need for a Zope Pack Manager.
Or maybe that should be Zope Package Manager? :)
It would be nice to have a single unified way of preparing apps,
products or whatever for distribution.
Jimmie Houchin wrote:
It would be nice to have a single unified way of preparing apps,
products or whatever for distribution. The process be nicely automated
or provide a user interface for building the distributable. The install
process would also need to be just as painless.
Totally agree.
Chris Withers writes:
Hi,
Zope currently has two ways of distributing products:
1. Tarballs containing python products
2. .zexps containing methods, ZClass products and the like.
Things are now getting bad as products are emerging (PTK, Tracker, etc)
which require both of these
