Sorry, but you are going wrong way. I ask you to fund way to do right installation in *setup.py*, not in Makefile. Otherwise gentoo-users will never use Cardapio, because distutils.eclass calls 'setup.py install -root=/var/tmp/portage/..../image' and expects that it will install files into /var/tmp/portage/..../image/usr/bin and /var/tmp/portage/.../image/usr/lib. If I use 'make PREFIX="/var/tmp/portage/..../image" install' in ebuild, it`s bad too: it installs into /var/tmp/portage/.../image/bin and /var/tmp/portage/.../image/lib.
P.S. Please read something about how portage works
P.P.S Also you can look at http://gitorious.org/batti/batti/blobs/master/setup.py, especially this line:
'scripts = [Constants.NAME]' which installs main executable to apropriate location.
Sorry, but you are going wrong way. I ask you to fund way to do right installation in *setup.py*, not in Makefile. Otherwise gentoo-users will never use Cardapio, because distutils.eclass calls 'setup.py install -root=/ var/tmp/ portage/ ..../image' and expects that it will install files into /var/tmp/ portage/ ..../image/ usr/bin and /var/tmp/ portage/ .../image/ usr/lib. If I use 'make PREFIX= "/var/tmp/ portage/ ..../image" install' in ebuild, it`s bad too: it installs into /var/tmp/ portage/ .../image/ bin and /var/tmp/ portage/ .../image/ lib. gitorious. org/batti/ batti/blobs/ master/ setup.py, especially this line:
P.S. Please read something about how portage works
P.P.S Also you can look at http://
'scripts = [Constants.NAME]' which installs main executable to apropriate location.