bug#67545: wrap-program gives different argv[0] for Python scripts

bug#67545: wrap-program gives different argv[0] for Python scripts

[Rikard Nordgren]

For example the meld package is using wrap-program and the name of the
actual meld executable will be .meld-real. The idea is that the -a
option to exec in the wrapper script should change the name of argv[0],
but for Python scripts this doesn't work. This means that when doing
"meld --version" it gives ".meld-real 3.22.0" instead of the expected
"meld 3.22.0". Any ideas on how this could be fixed?








När du har kontakt med oss på Uppsala universitet med e-post så innebär det att vi behandlar dina personuppgifter. För att läsa mer om hur vi gör det kan du läsa här: http://www.uu.se/om-uu/dataskydd-personuppgifter/

E-mailing Uppsala University means that we will process your personal data. For more information on how this is performed, please read here: http://www.uu.se/en/about-uu/data-protection-policy

bug#67545: wrap-program gives different argv[0] for Python scripts

[Maxim Cournoyer]

Hi,

Rikard Nordgren <rikard.nordgren@farmaci.uu.se> writes:

> For example the meld package is using wrap-program and the name of the
> actual meld executable will be .meld-real. The idea is that the -a
> option to exec in the wrapper script should change the name of argv[0],
> but for Python scripts this doesn't work. This means that when doing
> "meld --version" it gives ".meld-real 3.22.0" instead of the expected
> "meld 3.22.0". Any ideas on how this could be fixed?

We already have a solution, in the form of 'wrap-script'.  I have an old
series changing pyproject-build-system to use it instead of wrap-program
for core-updates, perhaps I should revive it.

-- 
Thanks,
Maxim