Name Date Size #Lines LOC

..--

MakefileH A D19-Jan-20181.5 KiB7345

READMEH A D17-Jan-20182.8 KiB6858

README.illumosH A D17-Jan-20182.9 KiB7355

africaH A D29-Oct-201850.6 KiB1,2651,130

antarcticaH A D29-Oct-201812.7 KiB344311

asiaH A D29-Oct-2018144.4 KiB3,3843,109

australasiaH A D29-Oct-201874.7 KiB1,8261,600

backwardH A D29-Oct-20184.5 KiB131127

continent.tabH A D17-Jan-2018257 1514

country.tabH A D02-May-20174.3 KiB275274

do_pofile.shH A D17-Jan-20181 KiB6945

etceteraH A D29-Oct-20182.7 KiB8170

europeH A D29-Oct-2018167.7 KiB3,9963,682

factoryH A D22-Nov-2017367 118

northamericaH A D29-Oct-2018147.4 KiB3,4503,197

southamericaH A D29-Oct-201886 KiB1,9671,863

systemvH A D29-Oct-20181.6 KiB4035

zone.tab.txtH A D29-Oct-201818.7 KiB449448

zone_sun.tabH A D29-Oct-201820.8 KiB472471

README

1Copyright (c) 1999, 2010, Oracle and/or its affiliates. All rights reserved.
2
3The /usr/share/lib/zoneinfo/src directory contains zoneinfo timezone source
4files.  These source files have been compiled using zic(1M) to create
5the zoneinfo data files in /usr/share/lib/zoneinfo.  The zic command can be
6used with the zoneinfo source files to create additional data files.
7
8The zoneinfo files track the Olson public source provided at
9ftp://elsie.nci.nih.gov/pub/, therefore zoneinfo files may be added and
10removed as the Solaris source is updated.  The current Solaris release of
11the zoneinfo files is based on tzdata2010k.tar.gz.
12
13The /usr/share/lib/zoneinfo/GMT[+-]* timezones listed below have been
14removed from the release.  Replace usage of the
15/usr/share/lib/zoneinfo/GMT[+-]* files with the equivalent quoted timezone
16(see environ(5)).  Note the signs of the offsets of the equivalent quoted
17timezone are reversed from the signs of the /usr/share/lib/zoneinfo/GMT[+-]*
18files.
19
20For example, replace TZ=:GMT+1, with TZ="<GMT-1>-1".  (The colon (:) is
21significant.  Without the colon, for example TZ=GMT+1, an unquoted timezone
22is used;  unquoted timezones are not affected by the removal of the zoneinfo
23timezone files listed below.)
24
25The following files have been removed from the release:
26
27/usr/share/lib/zoneinfo/GMT-12
28/usr/share/lib/zoneinfo/GMT-11
29/usr/share/lib/zoneinfo/GMT-10
30/usr/share/lib/zoneinfo/GMT-9
31/usr/share/lib/zoneinfo/GMT-8
32/usr/share/lib/zoneinfo/GMT-7
33/usr/share/lib/zoneinfo/GMT-6
34/usr/share/lib/zoneinfo/GMT-5
35/usr/share/lib/zoneinfo/GMT-4
36/usr/share/lib/zoneinfo/GMT-3
37/usr/share/lib/zoneinfo/GMT-2
38/usr/share/lib/zoneinfo/GMT-1
39/usr/share/lib/zoneinfo/GMT+1
40/usr/share/lib/zoneinfo/GMT+2
41/usr/share/lib/zoneinfo/GMT+3
42/usr/share/lib/zoneinfo/GMT+4
43/usr/share/lib/zoneinfo/GMT+5
44/usr/share/lib/zoneinfo/GMT+6
45/usr/share/lib/zoneinfo/GMT+7
46/usr/share/lib/zoneinfo/GMT+8
47/usr/share/lib/zoneinfo/GMT+9
48/usr/share/lib/zoneinfo/GMT+10
49/usr/share/lib/zoneinfo/GMT+11
50/usr/share/lib/zoneinfo/GMT+12
51/usr/share/lib/zoneinfo/GMT+13
52
53As zoneinfo timezones are updated, the savings/daylight transition rules
54and timezone name abbreviations may change.  This can affect how
55the times are calculated in the local timezone.  Therefore the interpretation
56of a time_t value can vary amongst Solaris releases that use different
57versions of the zoneinfo timezones.
58
59The zoneinfo timezone data files do not transition past
60Tue Jan 19 03:14:07 2038 GMT.  Therefore for 64-bit applications using
61zoneinfo timezones, calculations beyond this date may not use the correct
62offset from standard time, and could return incorrect values.  This affects
6364-bit versions of interfaces such as ascftime(3C), cftime(3C), ctime(3C),
64getdate(3C), ftime(3C), mktime(3C), and localtime(3C).
65
66For more information see zic(1M), zdump(1M), environ(5), TIMEZONE(4),
67ctime(3C), and mktime(3C) man pages.
68

README.illumos

1#
2# This file and its contents are supplied under the terms of the
3# Common Development and Distribution License ("CDDL"), version 1.0.
4# You may only use this file in accordance with the terms of version
5# 1.0 of the CDDL.
6#
7# A full copy of the text of the CDDL should have accompanied this
8# source.  A copy of the CDDL is also available via the Internet at
9# http://www.illumos.org/license/CDDL.
10#
11
12#
13# Copyright (c) 2014 Joyent, Inc.  All rights reserved.
14#
15
16How to update the TZ database information.
17
18Welcome! You've probably heard that some aspect of time has changed and
19you're wondering what to do. The first thing to do is to grab the latest
20version of the time database which can currently be found at:
21
22http://www.iana.org/time-zones
23
24You'll need the data tarball. Most data files are used in the gate
25directly; however, a few have slightly different names. The following
26commands assume that you're inside of the directory you extracted the
27time zone files.
28
29$ cp africa antarctica asia australasia backward etcetera europe \
30  northamerica pacificnew southamerica systemv $CODEMGR_WS/usr/src/data/zoneinfo
31
32Next you need to copy the country tab and the zone tab files. These have
33different names in our source tree.
34
35$ cp iso3166.tab $CODEMGR_WS/usr/src/data/zoneinfo/country.tab
36$ cp zone.tab $CODEMGR_WS/usr/src/data/zoneinfo/zone.tab.txt
37
38Now, you need to manaully fix up the zone_sun.tab. zone_sun.tab has
39additional different zone names that the original does not. As things
40are changed and removed, or coordinates updated, the same should be done
41in zone_sun.tab. The simplest way known to deal with it today is
42something like the following:
43
44$ cd $CODEMGR_WS/usr/src/data/zoneinfo
45$ vimdiff zone.tab.txt zone_sun.tab
46
47And as you see things that show up as egregiously different, do a 'git
48diff zone.tab.txt' and see what changed and fix zone_sun.tab
49appropriately. Usually this means deleting removed entries and adding
50new ones.
51
52After that's done, you'll need to go through the more agonizing process of
53packaging. To do this, you'll want to look through the differences that have
54occurred in zone.tab.txt and backward. The contents of backward describe
55hardlinks that need to exist in packaging. Specifically, if you have a line in
56the form of:
57
58LINK	Beleriand	Gondolin
59
60That instructs that Gondolin should be hardlinked to Beleriand. In ips parlance
61that'd be:
62
63hardlink path=usr/share/lib/zoneinfo/Beleriand target=./Gondolin
64
65The differences in zone.tab.txt describe the additions and removals of various
66file entries. If you're not friends with protocmp yet, this should help you out.
67Once both of those are done, you'll need to update the version of the package
68itself in the manifest. IANA releases these as <year><letter>, eg. 2013i.
69Instead, you need to encode that letter to its spot in the alphabet. So 2013i
70would become 2013.9.
71
72Once packaging is all done, then you should be all set.
73