#908 closed defect (wontfix)
--with-Xdummy --with-Xdummy_wrapper options not honored across invocations of setup.py
| Reported by: | jonathan.underwood | Owned by: | Antoine Martin |
|---|---|---|---|
| Priority: | minor | Milestone: | future |
| Component: | server | Version: | 0.15.x |
| Keywords: | Cc: |
Description (last modified by )
It used to be the case that you could specify --with-Xdummy --with-Xdummy_wrapper when running setup.py build to force selection of the Xdummy wrapper rather than Xvfb without having the Xorg detection stuff kick in. Subsequently, running a python setup.py --skip-build install (without --with-Xdummy --with-Xdummy_wrapper) would install an xpra.conf file which used Xdummy, as expected.
Currently, unless --with-Xdummy --with-Xdummy_wrapper is specified both with build and install, the Xorg detection stuff kicks in during install, and a xpra.conf using Xvfb is installed.
Logically, I expect xpra.conf to be created during build, and whatever is present during install is just installed if we're using --skip-build. I'm not sure when this crept in.
Change History (4)
comment:1 Changed 7 years ago by
| Description: | modified (diff) |
|---|---|
| Priority: | major → minor |
| Status: | new → assigned |
comment:2 Changed 7 years ago by
| Milestone: | 0.16 → future |
|---|
comment:3 Changed 6 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | assigned → closed |
Too hard to fix for little gain.
comment:4 Changed 16 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/908
copyleft 2010 - 2021
out of time, and this stuff is always harder than it looks - rescheduling
see also #977