Skip to content

demo: do not pip install ninja #1331

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

Merged
merged 1 commit into from
Feb 13, 2023
Merged

demo: do not pip install ninja #1331

merged 1 commit into from
Feb 13, 2023

Conversation

mythi
Copy link
Contributor

@mythi mythi commented Feb 13, 2023

ninja-build is installed as a dependency to meson so we don't need to install it separately. In fact pip install fails on setups that enforce PEP-668 of externally managed environments.

Signed-off-by: Mikko Ylinen [email protected]

ninja-build is installed as a dependency to meson so we don't need to
install it separately. In fact pip install fails on setups that enforce
PEP-668 of externally managed environments.

Signed-off-by: Mikko Ylinen <[email protected]>
@codecov-commenter
Copy link

Codecov Report

Merging #1331 (2e5c19c) into main (689c6ab) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1331   +/-   ##
=======================================
  Coverage   51.17%   51.17%           
=======================================
  Files          44       44           
  Lines        4879     4879           
=======================================
  Hits         2497     2497           
  Misses       2239     2239           
  Partials      143      143           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@tkatila tkatila merged commit e8a7d9f into intel:main Feb 13, 2023
@eero-t
Copy link
Contributor

eero-t commented Feb 13, 2023

If you're explicitly using ninja in later steps, IMHO would have been better to include ninja to package list. You might also consider --no-install-recommends, and listing needed extra packages explicitly.

@mythi
Copy link
Contributor Author

mythi commented Feb 13, 2023

If you're explicitly using ninja in later steps, IMHO would have been better to include ninja to package list. You might also consider --no-install-recommends, and listing needed extra packages explicitly.

true. currently ninja-build is a Depends dependency so --no-install-recommends can be enabled independently but you're right that adding it to be explicit makes sense

@mythi
Copy link
Contributor Author

mythi commented Feb 14, 2023

@eero-t updated as part of #1332

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.

4 participants