On Wednesday 09 July 2014 03:48:40 Matthew Thode wrote:
arm has a historical problem with stabilization, while keywording
doesn't require access to all arm sub-arches the problem with the
stabilization slowness causes running a full ~arm to become hard. By
that I mean that if someone keywords
On Tuesday 14 January 2014 22:37:19 William Hubbs wrote:
I think we need a global policy that either helps keep the stable tree
up to date or reverts an architecture to ~ over time if the arch team
can't keep up.
As a compromise solution for minor archs, it would be nice if there were a
Ohai,
As part of the RAP project[1], a version of Gentoo Prefix that uses its own
libc rather than relying on the host version, prefix needs some new profiles
serving this variant. While this is entirely inconsequential for most
packages, there are a handful of ebuilds that need to distinguish
On Sunday 03 November 2013 13:10:57 Tom Wijsman wrote:
Let's say I have the blocker:
dev-python/python-exec-1 is blocking
dev-lang/python-exec-0.3.1
We could have it additionally say something like:
To resolve this blocker, you can run one of the following commands:
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
