Problem ------- After installing zope-3.2.0 on an amd64 system in order to test it for keywording, the following error is generated when attempting to configure using: oberon ~ # emerge --config =zope-3.2.0 Configuring pkg... * Instance zope-3.2.0 creation, calling mkzopeinstance.. Could not locate Zope software installation! * Patching /var/lib/zope/zope-3.2.0/etc/zdaemon.conf sed: can't read /var/lib/zope/zope-3.2.0/etc/zdaemon.conf: No such file or directory * Default instance created at /var/lib/zope/zope-3.2.0 * Created default zope user 'admin' with password 'admin'. * System uid/gid for instance is: zope:zope. * To start instance (default ports 8080,8021) use: /etc/init.d/zope-3.2.0 start * To start instance on every restart use: rc-update -a zope-3.2.0 default On checking, the directory /var/lib/zope/zope-3.2.0/ then only includes an empty log file. The new default zope instance will not start. Analysis --------- pkg_config() calls mkzopeinstance. mkzopeinstance is a python script to generate a new zope instance that includes the following lines: for parts in [("src",), ("lib", "python"), ("Lib", "site-packages")]: <DELETIA> else: try: import zope.app.server except ImportError: print >>sys.stderr, "Could not locate Zope software installation!" sys.exit(1) The issue appears to be that the script references "lib", but the directory /usr/lib64/zope-3.2.0 contains a "lib64" directory. Renaming it to lib apparently resolves issue. This problem is apparently due to the fact that the ebuild properly uses multilib environment vars ($get_libdir) in some places, but some scripts are not aware of this fact.
amd64 guys - how is it generaly solved? patching or UPSTREAM? anyway, i have no access to (and knowledge of) amd64 dir layaouts - can someone provide more info here about paths being used?
upstream would be perfect, but often we end up patching it ourselfs
Fixed in net-zope/zope-3.3.0
