>@pavlinamv So then, how does date in GNU Coreutils do it?
rpm task:
_input_: time in an arbitrary time zone, the time zone description
_result_: the corresponding time in UTC.
Command ```date``` _prints_ or _sets_ the system date and time. Neither
_printing_, nor _setting_ is so complex (or the same as) as the rpm task.
If date is used for _printing_ of the system date and time then it uses
strftime() from time.h. This function can be used for printing of time zone
name or abbreviation that is stored in TZ. It can not be used for setting a
different time zone than is in TZ and time zone abbreviations can not be in
used TZ.
If date is used for _setting_ then input time can be in a different time zone
(than described in TZ) only if the timezone is UTC. Thus it can not be used for
setting time zone from an _arbitrary_ time zone abbreviation too.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/739#issuecomment-516006774
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
