Re: [Zope-dev] Zope Add-on Installation
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 to get a single product working which is horrible :/
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, DemoPortal is probably the closest) Tarballs are flexible enough to install both a Python Products and associated ZClasses from ZEXP's (the products "__init__" function imports the ZEXP at the appropriate place, if it is not already there).
I do not say, this is optimal. Dieter
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, DemoPortal is probably the closest)
Sadly tarballs only address issues 1 & 2 that I can see above... I wonder if ZPatterns Specialists address 3?
Tarballs are flexible enough to install both a Python Products and associated ZClasses from ZEXP's (the products "__init__" function imports the ZEXP at the appropriate place, if it is not already there).
I presume you mean the thing created by the 'Distribution' tab of products? cheers, Chris
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 Skins (none right now, DemoPortal is probably the closest)
Sadly tarballs only address issues 1 & 2 that I can see above...
I wonder if ZPatterns Specialists address 3?
Tarballs are flexible enough to install both a Python Products and associated ZClasses from ZEXP's (the products "__init__" function imports the ZEXP at the appropriate place, if it is not already there).
I presume you mean the thing created by the 'Distribution' tab of products?
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. -- Do not meddle in the affairs of sysadmins, for they are easy to annoy, and have the root password.
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 file (maybe a zexp?) and an __init__.py file that imports it for you and wraps them all up in a TarBall with the correct paths :-) cheers, Chris
Chris Withers wrote:
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 file (maybe a zexp?) and an __init__.py file that imports it for you and wraps them all up in a TarBall with the correct paths :-)
cheers,
Chris
Hmmm .. I don't seem to see any zexps in any of the distribution tabbed products I have. Admittedly, that isn't a high number :| -- Do not meddle in the affairs of sysadmins, for they are easy to annoy, and have the root password.
Bill Anderson wrote:
Chris Withers wrote:
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 file (maybe a zexp?) and an __init__.py file that imports it for you and wraps them all up in a TarBall with the correct paths :-)
cheers,
Chris
Hmmm .. I don't seem to see any zexps in any of the distribution tabbed products I have. Admittedly, that isn't a high number :|
The Distribution tab creates a gzip'ed archive with an __init__.py, a version.txt, and a product.dat. The file product.dat is pretty much a zexp but it has a couple of extra goodies in it for "configurability". 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. Shane
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 around anywhere? will it land in 2.2.1? cheers, Chris
participants (4)
-
Bill Anderson -
Chris Withers -
Dieter Maurer -
Shane Hathaway