libexo, Paths on amd64

[Mark Trompell]

Hi, is there a reason for installing pyexo.py, pyexo.pyc and pyexo.pyo
into /usr/lib/ instead of /usr/lib64/?
I use a conary (http://wiki.conary.com)based Linux Distribution and
conary prevents packages from installing into /usr/lib and/usr/lib64 at
the same time (it even prevents me from building such packages).
Just for illustration of my problem I add the output from conary.
So if there is no reason for using /usr/lib/ on x86_64 it would be nice
if you can change the paths for 0.4.
Best regards Mark

        error: NonMultilibComponent: python packages may install
        in /usr/lib or /usr/lib64, but not both: at
        least /usr/lib/python2.4/site-packages/pyexo.py
        and /usr/lib64/python2.4/site-packages/exo-0.3/exo/__init__.pyc
        both exist
        +
        Transient: /usr/lib64/python2.4/site-packages/exo-0.3/exo/__init__.pyo
        +
        Transient: /usr/lib64/python2.4/site-packages/exo-0.3/exo/__init__.pyc
        + Transient: /usr/lib/python2.4/site-packages/pyexo.pyo
        + Transient: /usr/lib/python2.4/site-packages/pyexo.pyc
        + SharedLibrary: /usr/lib64/libexo-0.3.so.0.0.0
        warning: EnforceConfigLogBuildRequirements:
        path /usr/bin/pygtk-codegen-2.0 suggests buildRequires:
        pygtk:devel
        warning: EnforceConfigLogBuildRequirements: Probably add to
        buildRequires: ['pygtk:devel']
        error: NonMultilibComponent: python packages may install
        in /usr/lib or /usr/lib64, but not both: at
        least /usr/lib/python2.4/site-packages/pyexo.py
        and /usr/lib64/python2.4/site-packages/exo-0.3/exo/__init__.pyc
        both exist
        Package Policy errors found:
        NonMultilibComponent: python packages may install in /usr/lib
        or /usr/lib64, but not both: at
        least /usr/lib/python2.4/site-packages/pyexo.py
        and /usr/lib64/python2.4/site-packages/exo-0.3/exo/__init__.pyc
        both exist