XQuartz updating, (possibly) downgrading and $DISPLAY
XQuartz updating, (possibly) downgrading and $DISPLAY
- Subject: XQuartz updating, (possibly) downgrading and $DISPLAY
- From: René J.V. Bertin <email@hidden>
- Date: Mon, 05 Dec 2016 10:10:50 +0100
Hi,
I've been running 2.7.7 (or .8) for quite a while (on OS X 10.9.5) without any real reason to update, but now that the gap is getting a bit big I'm thinking it might be time, also to see if that makes the xfwm4 glitch I just described go away.
2 questions:
- can I backup /opt/X11 and XQuartz.app in order to be able to roll back if something doesn't work out and cannot be sorted out in a reasonable amount of time? Anything else that should be backed up?
- somewhere back in the day I managed to get a standard $DISPLAY variable of the form :0 or hostname:0 . That's exactly what I want, I don't in fact want to allow applications to auto-start an X server for me; I mostly treat my X11 session as a kind of separate machine which can coerce the host but not be coerced by it if not on my explicit request.
The details of how I managed this have faded: is there something to tweak under /opt or inside the XQuartz appbundle?
With the earlier bundle-based .pkg format I'd just look through the pre- and post-flight scripts to see what kind of unexpected things an installer might do, but that's become complicated.
Thanks,
René
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden