The GLOBAL_CONFIG_PATH constants and DEPCACHE_PATH constants should be
relative to the installation prefix of portage itself, not the installation
prefix of packages it is installing.
---
pym/_emerge/actions.py |6 ---
pym/portage/_sets/__init__.py
This adds support for picking up the EPREFIX config setting from the EPREFIX
environment variable. An emerge --prefix option is added to specify it,
analogous to --root and --config-root options.
---
pym/_emerge/actions.py |3 ++-
pym/_emerge/main.py |7
Hi Ruud,
On 17-06-2013 09:21:41 +0200, Ruud Koolen wrote:
This patch series adds support for using a portage installed in one prefix
to build packages with a different prefix.
Thanks so much for your work. I hope to have a look at this soon, and
merge this. From your work I assume your
On Mon, 17 Jun 2013, at 01:00, Ruud Koolen thusly quipped:
I also didn't test whether these patches work on the prefix-portage branch. I
don't really know much far prefix-portage diverges from mainline portage, so I
don't know whether I should expect it to just work.
Prefix portage is
