Skip to content

Wrap pip install in a venv #8

@Rotonen

Description

@Rotonen

When using this action in a GitHub Action, which is wrapped by a container, in this specifically the Steam Linux SDK (registry.gitlab.steamos.cloud/steamrt/sniper/sdk), where the default user is root, the default behaviour of pip as root ends up conflicting with OS packages, breaking the setup.

For now I can circumvent by not using this action and manually installing conan as it's just a Python package in the end of the day.

To be able to use this action, this would also need addressing, as I am dealing with multiple build configurations at the same time: #6

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions