Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: zope3 - Zope 3 web application server framework https://bugzilla.redhat.com/show_bug.cgi?id=235672 bugzilla@xxxxxxxxxx changed: What |Removed |Added ---------------------------------------------------------------------------- Version|devel |rawhide timothy.selivanow@xxxxxxxxxxxxxxxxxx changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |timothy.selivanow@virtualxis | |tenz.com ------- Additional Comments From timothy.selivanow@xxxxxxxxxxxxxxxxxx 2008-03-18 18:58 EST ------- Minor rpmlint complaints: ./zope3.spec:13: E: hardcoded-library-path in /usr/lib/%{zope_pkgname} Change to /usr/%{_lib}/%{zope_pkgname} ./zope3.spec:101: W: rpm-buildroot-usage %build rm -rf %{buildroot} I see this was taken from the original zope 2.10.x spec, this should be removed. ./zope3.spec: W: mixed-use-of-spaces-and-tabs (spaces: line 3, tab: line 24) Simple to change. Make sure that you are using one method throughout the spec. Also, version 3.4.0c1 is newest upstream (http://www.zope.org/Products/Zope3/3.4.0c1/Zope-3.4.0c1.tgz), and curious on how this package and python-zope-interface might/could interact. I'm not happy (rpmbuild fails with lib change) with the directory structure that it creates under /usr/${_lib} either (e.g. /usr/lib64/zope3/lib64/python/BTrees/_OOBTree.so, would be nice to integrate more with %{python_sitearch} if possible), I imagine something like (for my given example) /usr/lib64/python2.5/zope/BTrees/_OOBTree.so would be more appropriate. It's been a while since anyone has commented on this, does this have any backing? I'm slightly interested as I've wanted to work with Zope and I re-build the f6 packages for use on CentOS. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review