Bruno, thank you for pointing that out. I agree. This introduces a new use case: to be able to install Python packages to the system and not into a virtualenv. It also made us think about root as being a requirement for running this playbook with its defaults. I've updated the two tickets that deal w/ those aspects. The virtualenv will default to "/usr/local/pulpenv", it can be overridden, and if unset will install to the system package store. Edit references are below:
https://pulp.plan.io/issues/3716#note-5 https://pulp.plan.io/issues/3723#note-6 Other feedback, ideas, questions, or concerns are welcome. On Fri, Jun 8, 2018 at 11:01 AM, Bruno Rocha <[email protected]> wrote: > Just a note: As containers are already isolated from the hosting system I > think that a Virtualenv is an unnecessary layer inside a container, we can > just install the packages in the container's Python environment. > > -- > Bruno Rocha > Senior Quality Engineer > Red Hat >
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
