Please don't pull gruesome hacks around time_t problems. If the code is gross and complex, it is probably because it was forgotten for a long time. The upstream authors might appreciate having their attention focused on it.
Make them aware that larger and more varied types for time_t are coming into the software ecosystem -- work with them. You may be suprised. They may wekcome the opportunity to refactor the code properly.
