This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients FFY00, christian.heimes, frenzy, hroncok, jaraco, lemburg, petr.viktorin, steve.dower
Date 2021-05-05.09:04:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <678748bb-3d15-bec2-e4a7-4f354fb47e25@egenix.com>
In-reply-to <1620203362.3.0.901254535882.issue43976@roundup.psfhosted.org>
Content
On 05.05.2021 10:29, Christian Heimes wrote:
> 
> I mean that Steve and you are talking about different things.

Could be. I was addressing the point Steve made about not allowing
or making it hard to run "pip install" as root user.

> Neither Steve nor you or I are are Linux distro packaging experts. I suggest that we listen to the expertise of downstream packagers like Filipe or Miro. They deal with packaging on a daily basis.

Agreed.

> By the way you are assuming that all container solutions work like Docker and that all Docker and non-Docker based container solutions allow you to run code as unrestricted, unconfined root. That's a) a incorrect, and b) offtopic for this ticket.

I gave the Docker example as proof that running "pip install" as
root is a rather common scenario and needs to be supported.

Linux distros have been supporting this for many years and just
because distutils is deprecated should not mean that we no longer
provide ways to support this kind of setup.

BTW: I'm aware that other container solutions work in different ways,
e.g. Podman, LXC, etc. but I have yet to find a solution that doesn't
offer root permissions inside the containers (I'm not talking
about how the container is run in the host system).
History
Date User Action Args
2021-05-05 09:04:02lemburgsetrecipients: + lemburg, jaraco, christian.heimes, petr.viktorin, steve.dower, hroncok, frenzy, FFY00
2021-05-05 09:04:02lemburglinkissue43976 messages
2021-05-05 09:04:01lemburgcreate