Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:36633
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain debian.org from 66.93.22.232 cause and error)
To: ceo@l-i-e.com
Date: Fri, 28 Mar 2008 00:45:59 +0100
User-Agent: KMail/1.9.9
Cc: internals@lists.php.net,
 "Joe Orton" <jorton@redhat.com>
References: <20080109141541.GA14571@redhat.com> <200803201840.17473.seanius@debian.org> <49163.98.193.37.55.1206653217.squirrel@www.l-i-e.com>
In-Reply-To: <49163.98.193.37.55.1206653217.squirrel@www.l-i-e.com>
MIME-Version: 1.0
Content-Type: multipart/signed;
  boundary="nextPart3021813.FAWotJ1fuv";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-ID: <200803280046.02297.seanius@debian.org>
Subject: Re: [PHP-DEV] [PATCH] date/timelib: use system timezone database
From: seanius@debian.org (sean finney)

--nextPart3021813.FAWotJ1fuv
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

hi,

On Thursday 27 March 2008 10:26:57 pm Richard Lynch wrote:
> Just recently, somebody wondered why PHP had the CORRECT time when
> their web-server didn't...

and vice versa. see for example:

	http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D471104

if there were an *option* for php to use the system-bundled timezone databa=
se,=20
then this would be a moot point.  =20

but instead, at this point to solve the problem someone will need to go=20
digging through cvs, produce a changeset, possibly massage the patch to app=
ly=20
to an older release, ensure the software builds correctly, test the new=20
packages locally, create a new official release for the stable distribution=
,=20
wait for the users to get the update...

this is a process that has been done once already for the system timezone=20
database packages, why do it again for php?  if the admin is using the=20
packaged versions of php (and that is the point of this discussion), it won=
't=20
magically fix itself... so *something* has to be upgraded.  and either way=
=20
they're usually running "$packagemanager upgrade", taking whatever is new,=
=20
whether it is just the timezonedb or the php packages too.  it's merely a=20
question of "get the updates for free?" vs "get the updates when the system=
=20
*and* php has been updated?"

> As I understand the situation, if you can get ALL the sysadmins of the
> world to update their [bleep] timezonedb frequently, PHP can drop the
> internal timezonedb.

usually that's a matter of "$packagemanager upgrade" but i digress. =20

of course if you're in a hosted environment where you've built your own php=
=20
but don't have root to update the system timezone db, then it can be very=20
useful to have the bundled timezonedb too. =20

but ultimately, what may be best for you may be least optimal for someone=20
else... so why not provide an option to work both ways?  i'm not even askin=
g=20
that this be made the default, in case you're worried about the clueless=20
user/sysadmin factor.



	sean

--nextPart3021813.FAWotJ1fuv
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBH7DG6ynjLPm522B0RAsWVAJ9hPugqGyyKHqnTQo1cITa//A8LUQCfaYmR
uMde+h4K4kyICgObB9PnILg=
=ANdO
-----END PGP SIGNATURE-----

--nextPart3021813.FAWotJ1fuv--