| 1 |
On 7/5/10, Helmut Jarausch <jarausch@××××××××××××××××.de> wrote: |
| 2 |
> instead of |
| 3 |
> /var/tmp/portage/media-gfx/exact-image-0.8.1/image//usr/lib64/ |
| 4 |
> python2.6/site-packages |
| 5 |
> |
| 6 |
> there is a file |
| 7 |
> /var/tmp/portage/media-gfx/exact-image-0.8.1/image |
| 8 |
> /usr/lib/python2.5/site-packages |
| 9 |
|
| 10 |
I found something related to that. The install path seems to be |
| 11 |
semi-hardcoded in the sources, at api/python/Makefile: |
| 12 |
|
| 13 |
$(Q)mkdir -p $(DESTDIR)$(libdir)/python2.5/site-packages/ |
| 14 |
|
| 15 |
That will create a path suitable for python version 2.5 (maybe that |
| 16 |
one box of yours still has it?), but no others. |
| 17 |
|
| 18 |
I filed a bug (#327171). |
| 19 |
|
| 20 |
-- |
| 21 |
Arttu V. |
Archives