From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] php.ini: set date.timezone to UTC
Date: Sat, 02 May 2015 09:18:58 -0300 [thread overview]
Message-ID: <5544C0B2.2010107@zacarias.com.ar> (raw)
In-Reply-To: <5544BFEE.5020603@je-eigen-domein.nl>
On 05/02/2015 09:15 AM, Floris Bos wrote:
> I do know Debian has a patch to let PHP use the system's timezone
> database instead of the internal one.
> We could borrow that one, but then we would be deviating from upstream
> (which did not want the patch, and prefers to stick with their internal
> db).
As far as i remember it's a chicken-and-egg problem.
PHP is used in many old distros/systems that don't have modern tzdata
and that was a problem, so they bundled it (also cross-operating system
consistent behaviour).
But then the bundled one might be out of date as well, and takes up space :)
IMHO it should be a build-time php option.
Regards.
next prev parent reply other threads:[~2015-05-02 12:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 18:12 [Buildroot] [PATCH] php.ini: set date.timezone to UTC Floris Bos
2015-05-01 18:12 ` [Buildroot] [PATCH v2 1/3] php: fpm sapi: install startup script Floris Bos
2015-05-01 22:34 ` Arnout Vandecappelle
2015-05-01 22:58 ` Floris Bos
2015-05-01 23:06 ` Arnout Vandecappelle
2015-05-01 23:07 ` Arnout Vandecappelle
2015-05-02 7:44 ` Thomas Petazzoni
2015-05-01 18:12 ` [Buildroot] [PATCH v2 2/3] php: fpm sapi: install php-fpm.conf Floris Bos
2015-05-01 22:36 ` Arnout Vandecappelle
2015-05-02 7:45 ` Thomas Petazzoni
2015-05-01 18:12 ` [Buildroot] [PATCH v2 3/3] lighttpd: add option to enable php-fpm configuration Floris Bos
2015-05-02 21:17 ` Arnout Vandecappelle
2015-05-01 22:23 ` [Buildroot] [PATCH] php.ini: set date.timezone to UTC Arnout Vandecappelle
2015-05-01 23:08 ` Floris Bos
2015-05-02 7:49 ` Arnout Vandecappelle
2015-05-02 12:15 ` Floris Bos
2015-05-02 12:18 ` Gustavo Zacarias [this message]
2015-05-02 15:09 ` Floris Bos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5544C0B2.2010107@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.