New issue
Advanced search Search tips

Issue 715754 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Including portage in python venv

Project Member Reported by dgarr...@chromium.org, Apr 26 2017

Issue description

It's necessary to include portage in our python virtual environment if we plan to use the venv everywhere.

Currently, we have a number of packages that include it conditionally based on being inside the chroot or not. This is problematic in the first place, and breaks totally if the venv is used inside the chroot.

I'd like some solution that makes it available inside the venv, but would also like to keep in sync with the chroot version. I'm not certain of the best way to manage this.
 
Note... this bug is motivated by this CL:

https://chromium-review.googlesource.com/c/483940/

Comment 2 by aut...@google.com, May 5 2017

Labels: -current-issue
Labels: -Pri-2 Pri-3
Status: Assigned (was: Untriaged)
Status: WontFix (was: Assigned)
I believe the right solution to this is to keep importing portage from the chroot and refactor how that is handled in the code.  There are ways to conditionally use portage that are much better than what we currently do.

I don't think it's a good idea to package portage separately since it is tied to the chroot/OS packaging system.

Sign in to add a comment