Hello, everyone.

Following the last meeting approval, I've started working on cleaning up
sys-apps/portage, and making it use EAPI=5 and python-r1. While at it,
I found a few difficulties, pretty closely related to how we install
portage now.

I believe we need to change that to make the ebuild cleaner. If someone
has some spare time, I'd appreciate fixing the portage code.


Current install
---------------

1. .py files are installed in /usr/lib/portage/pym and byte-compiled
with active python interp,

2. emerge and other tools prepend /usr/lib/portage/pym to use those
files [bytecode conflict possible],

3. site-packages contains only symlinks to .py files,

4. some of python modules in portage use paths relative to .py file to
access /usr/lib/portage/bin.


New install
-----------

1. no /usr/lib/portage/pym (it's not really necessary with
python_targets),

2. all python modules & bytecode in site-packages,

3. emerge and other tools load portage from site-packages [proper
bytecode used],

4. but python modules need to be able to locate /usr/lib/portage/bin
somehow.


What needs to be done
---------------------

1. either:

a) we make portage capable of finding /usr/lib/portage/bin when .py
files are in site-packages (but don't break running from checkout!),

b) we install all of bin/* to site-packages as well (some python
packages simply do that).

2. extra kudos for replacing that ugly Makefile with setup.py.


Any thoughts? Anyone willing to do the work? Otherwise, I'll do it
myself if nobody beats me up to it.

Attaching work-in-progress portage-9999-r1 ebuild. Don't install it or
your system will be broken :).

-- 
Best regards,
Michał Górny