M.-A. Lemburg | 6 Jun 22:11
Favicon

Installing mxODBC Zope DA for use in Plone 3.x

The Plone universal installer ships with its own Python and Zope
installation. As a result the installation procedure for our
Zope DA has to be adapted to the Plone setup.

The following assumes that you are using the unified Plone 3.1
installer and its default standalone configuration.

For a Plone 3.1 standalone installation:
----------------------------------------

cd /opt/Plone-3.1/

# Unzip the mxODBC Zope DA ZIP file in the instance directory
unzip -d zinstance/parts/instance \
     egenix-mxodbc-zopeda-1.0.10.*-py2.4_ucs2.zip

# Move the product package into place
mv zinstance/parts/instance/lib/python/Products/mxODBCZopeDA \
     zinstance/products/

# Remove the no longer needed Products/ directory to avoid
# confusion
rmdir zinstance/parts/instance/lib/python/Products

then install the license files into

/opt/Plone-3.1/zinstance/parts/instance/lib/python/mx/ODBC

and restart Plone.

(Continue reading)

Martijn Pieters | 6 Jun 23:03
Favicon

Re: Installing mxODBC Zope DA for use in Plone 3.x

On Fri, Jun 6, 2008 at 10:14 PM, M.-A. Lemburg <mal@...> wrote:
> The Plone universal installer ships with its own Python and Zope
> installation. As a result the installation procedure for our
> Zope DA has to be adapted to the Plone setup.

How about providing a packaging without the lib/python/Products path?
Many a setup uses the standard extra-products-paths feature of zope
where additional directories are part of the Products namespace. This
would also allow automated inclusion into a buildout simply by using
the productdistros recipe (where you specify a URL of a compressed
Product archive to install).

--

-- 
Martijn Pieters

_______________________________________________________________________
eGenix.com User Mailing List                     http://www.egenix.com/
https://www.egenix.com/mailman/listinfo/egenix-users

M.-A. Lemburg | 6 Jun 23:29
Favicon

Re: Installing mxODBC Zope DA for use in Plone 3.x

On 2008-06-06 23:03, Martijn Pieters wrote:
> On Fri, Jun 6, 2008 at 10:14 PM, M.-A. Lemburg <mal@...> wrote:
>> The Plone universal installer ships with its own Python and Zope
>> installation. As a result the installation procedure for our
>> Zope DA has to be adapted to the Plone setup.
> 
> How about providing a packaging without the lib/python/Products path?
> Many a setup uses the standard extra-products-paths feature of zope
> where additional directories are part of the Products namespace. This
> would also allow automated inclusion into a buildout simply by using
> the productdistros recipe (where you specify a URL of a compressed
> Product archive to install).

The Zope DA relies on the mx package which must be installed as
top-level package, so simply removing the lib/python/Products path
is not really an option, AFAIK. Would love to be proven wrong :-)

For the next release we'll ship a version that's easier to install
and integrates into Plone and other buildout-based setups using
either a special recipe or as egg - among other enhancements, of
course.

We'll start working on that after we've kicked off the public beta for
our new mxODBC Connect product next week. A new mxODBC Connect Zope DA
will follow soon after the final release of the Python product.

--

-- 
Marc-Andre Lemburg
eGenix.com

(Continue reading)

Martijn Pieters | 7 Jun 00:14
Favicon

Re: Installing mxODBC Zope DA for use in Plone 3.x

On Fri, Jun 6, 2008 at 11:29 PM, M.-A. Lemburg <mal@...> wrote:
> The Zope DA relies on the mx package which must be installed as
> top-level package, so simply removing the lib/python/Products path
> is not really an option, AFAIK. Would love to be proven wrong :-)

Right, I forgot, sorry! You could just unbundle the two and specify
the dependency. :-)

> For the next release we'll ship a version that's easier to install
> and integrates into Plone and other buildout-based setups using
> either a special recipe or as egg - among other enhancements, of
> course.

Make it a Products. egg like current CMF* and CMFPlone practice (see
their respective svn repositories; basically just put it in a Products
directory with setuptools namespace declaration and rigging). You
should be able to provide old-style packagings as well still.

--

-- 
Martijn Pieters

_______________________________________________________________________
eGenix.com User Mailing List                     http://www.egenix.com/
https://www.egenix.com/mailman/listinfo/egenix-users


Gmane