| 1 |
>> |
| 2 |
>> Is the USE flag the right approach? Can we default the switch to be |
| 3 |
>> on for macos? |
| 4 |
> |
| 5 |
> Does it work on 10.4 as well? If so, we can just use a CHOST check |
| 6 |
> for |
| 7 |
> *-darwin*, otherwise, just check for *-darwin9 and enable it based |
| 8 |
> upon |
| 9 |
> that. I think it makes sense to enable it without USE-flag, provided |
| 10 |
> DISPLAY=:0.0 also still works when launchd socket support is enabled. |
| 11 |
|
| 12 |
I'm not sure, I no longer have access to 10.4 for testing, but I think |
| 13 |
that the new DISPLAY variable was only introduced in 10.5. From what |
| 14 |
I saw of the code enabling it only seems to make the connection |
| 15 |
process try the new DISPLAY variable format (which just points to a |
| 16 |
different socket then the normal unix socket DISPLAY variable I |
| 17 |
guess), so it shouldn't break anything if the support is there. |
| 18 |
|
| 19 |
Do we have any 10.4 users who could test this out? |
| 20 |
|
| 21 |
John |
Archives