From: Ruud Koolen <redlizard@redlizard.nl>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] [PATCH 0/3] Add cross-prefix support
Date: Mon, 17 Jun 2013 09:21:41 +0200 [thread overview]
Message-ID: <201306170921.41945.redlizard@redlizard.nl> (raw)
This patch series adds support for using a portage installed in one prefix
to build packages with a different prefix.
The current portage has a single EPREFIX variable specifying both the prefix
of the portage installation, and the prefix of the packages portage is
building. This patch series splits it into two parts: the
portage.const.EPREFIX variable specifying the prefix of the portage
installation, used for constructing the PATH as well as the paths to files
belonging to a portage installation itself rather than a target root; and the
EPREFIX setting in config instances, specifying the prefix of the
to-be-built packages and being used for almost everything else.
The EPREFIX config setting defaults to const.EPREFIX, but can be overridden
by the EPREFIX environment variable, as well as the emerge --prefix option.
This allows one to install systems with different prefixes using
`EPREFIX=/foo emerge @system`, though some unrelated changes need to happen
elsewhere first in order to make that a reality.
Ruud Koolen (3):
Distinguish between portage prefix and package prefix
Based GLOBAL_CONFIG_PATH and DEPCACHE_PATH on portage prefix
Pick up EPREFIX environment variable
bin/dispatch-conf | 2 +-
bin/portageq | 2 +-
pym/_emerge/actions.py | 9 +----
pym/_emerge/main.py | 7 ++++
pym/portage/_legacy_globals.py | 3 +-
pym/portage/_sets/__init__.py | 3 --
pym/portage/const.py | 34 ++++++++++----------
pym/portage/dispatch_conf.py | 2 +-
.../package/ebuild/_config/LocationsManager.py | 22 -------------
pym/portage/package/ebuild/config.py | 21 ------------
pym/portage/package/ebuild/doebuild.py | 2 +-
pym/portage/package/ebuild/fetch.py | 4 --
pym/portage/tests/resolver/ResolverPlayground.py | 3 +-
pym/portage/util/env_update.py | 3 +-
14 files changed, 34 insertions(+), 83 deletions(-)
--
1.7.2.5
next reply other threads:[~2013-06-17 7:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 7:21 Ruud Koolen [this message]
2013-06-17 7:23 ` [gentoo-portage-dev] [PATCH 1/3] Distinguish between portage prefix and package prefix Ruud Koolen
2013-06-17 7:23 ` [gentoo-portage-dev] [PATCH 2/3] Based GLOBAL_CONFIG_PATH and DEPCACHE_PATH on portage prefix Ruud Koolen
2013-06-17 7:24 ` [gentoo-portage-dev] [PATCH 3/3] Pick up EPREFIX environment variable Ruud Koolen
2013-06-17 7:53 ` [gentoo-portage-dev] [PATCH 0/3] Add cross-prefix support Fabian Groffen
2013-06-17 8:00 ` Ruud Koolen
2013-06-17 11:44 ` gmt
2013-06-18 21:07 ` Zac Medico
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201306170921.41945.redlizard@redlizard.nl \
--to=redlizard@redlizard.nl \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox