Bug 4279 - re-running tl-setup might screw up python-thinlinc symlink
Summary: re-running tl-setup might screw up python-thinlinc symlink
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Server Installer (show other bugs)
Version: pre-1.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.13.0
Assignee: Pierre Ossman
Keywords: prosaic
Depends on:
Reported: 2012-05-03 13:50 CEST by Pierre Ossman
Modified: 2021-06-21 12:20 CEST (History)
0 users

See Also:
Acceptance Criteria:


Description Pierre Ossman cendio 2012-05-03 13:50:48 CEST
If you do not want to run the standard Python, you start the installer (or tl-setup) with PYTHON set to whichever Python you want. That one will then be used by every other portion of ThinLinc via the python-thinlinc symlink.

It is very easy to undo this work though, as re-running tl-setup and forgetting to set PYTHON results in tl-setup reverting to the standard Python. This gets worse with the new menu icon, where it is impossible to specify a special interpreter.

We should consider having tl-setup (and possibly install-server) respect any python-thinlinc currently set. That would also make the policy of "when in doubt, run tl-setup" more safe.
Comment 1 Pierre Ossman cendio 2012-05-03 13:51:16 CEST
Note that this is mostly a Solaris problem as that's generally the only place where you tend to have multiple Python installations.
Comment 2 Pierre Ossman cendio 2021-06-21 12:20:12 CEST
The ability to choose Python interpreter was removed on bug 7566 as we don't see a need for it on our current platforms. Hence this is no longer an issue.

Note You need to log in before you can comment on or make changes to this bug.