I uploaded a set of packages last night which extend Python or Zope (in ways similar to the 'perl-<foo>' packages). I have a couple of questions about the work I did:
- The Python add-ons just do the "simplest thing", which is to drop the various artifacts into '<prefix>/lib/python/site-packages'. They do not create package-specific directories under '<prefix>/lib'. An alternate approach would be to create such a directory, e.g. '<prefix>/lib/python-<bar>', and then drop a 'bar.pth' file into the 'site-packages' directory. - The Zope add-ons *do* create a package-specific lib directory, and then symlink the actual Product directory from there into the Zope "instance home" products directory, '<prefix>/var/zope/Products'. The difference in approach is due to the fact that I just used Python's distutils support to install the Python add-ons, whereas I was following my earlier model (from the 'zope-cmf' package) for the Zope add-ons. Which approach fits better with the OpenPkg way? Tres. -- =================================================================== Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List openpkg-dev@openpkg.org
