Page MenuHomeFreeBSD

misc/zoneinfo: split BACKWARD into two options for recent/ancient backward compatibility
Needs ReviewPublic

Authored by andrew_tao173.riddles.org.uk on Apr 24 2020, 9:54 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mar 8 2024, 1:20 AM
Unknown Object (File)
Dec 22 2023, 11:30 PM
Unknown Object (File)
Nov 29 2023, 9:29 PM
Unknown Object (File)
Nov 27 2023, 10:25 AM
Unknown Object (File)
Nov 23 2023, 5:44 PM
Unknown Object (File)
Nov 9 2023, 8:35 PM
Unknown Object (File)
Nov 7 2023, 8:50 PM
Unknown Object (File)
Oct 8 2023, 7:27 PM
Subscribers

Details

Reviewers
skreuzer
Summary

This patch splits the BACKWARD option into separate BACKWARD and BACKWARD20 options, the first of which includes only changes since 2000a (which respect the current naming scheme) while the second includes all of the old garbage as well.

Make BACKWARD the default.

Note that matching the base system's recent behavior change (see D24306) would require making BACKWARD20 the default instead, but I think this is a better solution.

2000 as a cutoff date was chosen because (a) convenient round number and (b) it excludes all the old misnamed zones like GB-Eire.

(Note that this depends on updating to 2020a first)

Diff Detail

Repository
rP FreeBSD ports repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

I have no objection to this patch but I worry about FreeBSD diverging more from other operating systems. People have expectations about backwards compatible timezone lines existing. Breaking software gratuitously because we have a subset of compat links (even if the compat links by themselves are long stale) would not be cool.

I think a discussion about a split between backward and backward2000 should take place on the tz@iana.org mailing list rather than in a review for a FreeBSD ports patch.

Could you please start a discussion about this upstream?