Re: [gentoo-portage-dev] [PATCHES] setup.py install for Portage

[Brian Dolbec]

On Thu, 21 Aug 2014 22:19:38 +0200
Michał Górny <mgorny@g.o> wrote:


> In particular, tools that want to play with Portage internals need to
> export proper PORTAGE_BIN_PATH and PORTAGE_PYM_PATH before spawning
> them. The correct values can be obtained using portageq:
>
>   $ portageq envvar PORTAGE_BIN_PATH
>   /usr/lib/portage/python3.4
>   $ portageq envvar PORTAGE_PYM_PATH
>   /usr/lib64/python3.4/site-packages
>
>
> Please look through the patches and test at will :). Thanks.
>
> --
> Michał Górny
>
>

There is breakage in catalyst runs.  

[08:26] <iamben> has anyone tried mgorny's new portage ebuild? after
portage is emerged for stage1, it's missing /usr/lib/portage/bin/
altogether, for me

I did a search thru the catalyst code.  It is hard-coded in only 1
place:

lines 35, 37 in stage1-controller.sh

code snipit:

	clean)
		# Clean out man, info and doc files
		rm -rf usr/share/{man,doc,info}/*
		# Zap all .pyc and .pyo files
		find . -iname "*.py[co]" -exec rm -f {} \;
		# Cleanup all .a files except libgcc.a, *_nonshared.a and 
                # /usr/lib/portage/bin/*.a
		find . -type f -iname "*.a" | grep -v 'libgcc.a' | \
			grep -v 'nonshared.a' | grep -v	'/usr/lib/portage/bin/' | \ 
                        grep -v 'libgcc_eh.a' | xargs rm -f
	;;

	*)

Michał can you supply me a patch to fix this in catalyst and I will apply it.

I haven't started testing myself yet.
-- 
Brian Dolbec <dolsen>