Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bootstrap-prefix: use full path for do_emerge_pkgs #37

Closed
wants to merge 1 commit into from

Conversation

Kangie
Copy link
Contributor

@Kangie Kangie commented May 28, 2024

In the stage3 bootstrap we always prefer to use tools that have been built for stage3; to accomplish this we ensure that it is the first thing evaluated in PATH. Unfortunately, Portage, Python, and Python-exec are often pulled into the depgraph at some point before we're fully boostrapped. To ensure that we don't try and execute ${EPREFIX}/usr/bin/emerge before we're ready, always provide the full path to the bootstrap Python interpreter and emerge script.

In the stage3 bootstrap we always prefer to use tools that have been built for
stage3; to accomplish this we ensure that it is the first thing evaluated in PATH.
Unfortunately, Portage, Python, and Python-exec are often pulled into the depgraph
at some point before we're fully boostrapped. To ensure that we don't try and execute
${EPREFIX}/usr/bin/emerge before we're ready, always provide the full path to the
bootstrap Python interpreter and emerge script.

Signed-off-by: Matt Jolly <[email protected]>
@thesamesam thesamesam requested a review from grobian May 28, 2024 03:47
@grobian
Copy link
Member

grobian commented May 28, 2024

this makes sense, please push

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants