We "could" try to geolocate from ubiquity when in greeter mode but that's the only way I see us doing something like that.
We already are missing a Language => Default country mapping database so doing Language => timezone would be even more problematic and almost consistently wrong.
Attempting a call to the geolocation API as a Network Manager hook or something similar might work, doing it in ubiquity wouldn't work for users choosing to start the live session directly without going through the greeter.
One problem I see here is code duplication as we're currently quite carefully calling tzsetup that does all the for us and avoid having a duplicate copy of the logic from d-i. Having that call earlier in ubiquity or in a NM hook means duplicating the code and ending up having to maintain it at both places.
We "could" try to geolocate from ubiquity when in greeter mode but that's the only way I see us doing something like that.
We already are missing a Language => Default country mapping database so doing Language => timezone would be even more problematic and almost consistently wrong.
Attempting a call to the geolocation API as a Network Manager hook or something similar might work, doing it in ubiquity wouldn't work for users choosing to start the live session directly without going through the greeter.
One problem I see here is code duplication as we're currently quite carefully calling tzsetup that does all the for us and avoid having a duplicate copy of the logic from d-i. Having that call earlier in ubiquity or in a NM hook means duplicating the code and ending up having to maintain it at both places.
Anyway, marking as wishlist.