pip/setuptools: Entry points not visible from pkexec-root-environment

[Thomas Passin]

Pip is fine for most packages, as it looks like you know.  Some distros 
put some packages in unusual places, and those are the ones that either 
are not or should not be installed via pip.  Which ones varies from 
distro to distro. (I just include this  information here for others who 
haven't discovered it yet).

You asked for something that's not a hack, but here's a hack anyway :). 
Worth reading for the caveats -

https://stackoverflow.com/questions/50783033/execute-pkexec-command-on-a-different-path

I think the most natural way is to launch it with a script that adds 
your desired path to the pkexec environment.  What I don't know is if 
that script needs elevated permissions itself, but you probably already 
know about that.

On 12/18/2022 2:23 PM, c.buhtz at posteo.jp wrote:
> Dear Gerard,
> thank you for your reply.
> 
> Am 18.12.2022 19:45 schrieb Weatherby,Gerard:
>> "sudo python3 -m pip
>> install -e ."
>>
>> You’ve already started down a problematic road. I recommend installing
>> root level Python packages through your system package manager. (apt
>> for debian, or whatever RedHat is using now).
> 
> I'm totally with you at this point.
> 
> It is clear for me that distro maintainers sometimes using different 
> mechanics.
> But I'm the upstream maintainer and before handing offer a release to 
> the distro that thing need to run without a distro. And that is pip. I 
> also know a quit old project using "make" for that.
> 
> This question is independent from distros.
> 
>> I’ve never used pkexec. Generally, just use sudo.
> 
> They are two very different things. There is a strict reason why I need 
> to use pkexec here.
>