| 1 |
Am 28.07.2014 17:03, schrieb Micha³ Górny: |
| 2 |
> Hello, everyone. |
| 3 |
> |
| 4 |
> New install ----------- |
| 5 |
> |
| 6 |
> 1. no /usr/lib/portage/pym (it's not really necessary with |
| 7 |
> python_targets), |
| 8 |
|
| 9 |
We need to make that emerge -C prevents the removal of the last python |
| 10 |
version for which portage is installed then. That may already work. |
| 11 |
|
| 12 |
> |
| 13 |
> 2. all python modules & bytecode in site-packages, |
| 14 |
> |
| 15 |
> 3. emerge and other tools load portage from site-packages [proper |
| 16 |
> bytecode used], |
| 17 |
|
| 18 |
Other tools already do that. Emerge is a different thing. It's not a |
| 19 |
tool based on portage. emerge and portage are two large, |
| 20 |
interconnected things. (run "git grep _emerge" in pym/portage) |
| 21 |
|
| 22 |
> |
| 23 |
> 4. but python modules need to be able to locate |
| 24 |
> /usr/lib/portage/bin somehow. |
| 25 |
> |
| 26 |
> |
| 27 |
|
| 28 |
What about hardcoding this path at install time? Looking at pkgcore |
| 29 |
might give you some hints. |
Archives