Guys,
You don't need to read the whole of the history below, but doing so might
help to illustrate some of the confusion caused by distributing PHP release
candidates and extension packs on the php.net downloads page alongside the
official PHP releases.
Can we re-think this policy, please?
My own feeling is that RCs shouldn't be announced in this way, but I know
you all want a broad test base for them.
Perhaps we could make them available via a separate download page with a
header and text making it fully clear these are not PHP releases?
- Steph
----- Original Message -----
From: "Steph" steph@zend.com
To: "Joshua Seward" jseward@columbus.rr.com; "PHP-GTK dev"
php-gtk-dev@lists.php.net
Sent: Saturday, October 01, 2005 4:10 PM
Subject: Re: [PHP-GTK-DEV] PHP-GTK2 mysql Extensions?
Hi Josh,
Sorry, blame the weekend - I was AFK for the whole of this thread.
The snapshot version of PHP is created directly from CVS. It is not the
same version as those available on php.net. The only 5_1 version you
could
possibly have picked up from php.net is a release candidate dating back
two
months. There've been a lot of changes since then, including a Zend API
version bump which will prevent recent extensions from working with that
version of PHP. As Frank suggested, you can run php -v to check the PHP
version you have there. Next time you report a problem, running php-v and
copy/pasting the output in your first email would make it much easier for
us
all to understand what's going on.The extensions in the snaps zip work with the snapshot version of php.exe,
and you load them in exactly the same way as you normally would, which is:extension = php-gtk2.dll
extension = php_mysql.dllunlike PHP-GTK extensions, which are written as a comma-separated list.
php_mysql.dll isn't available in PECL, and never has been. That's why
it's
in the snaps zip, along with the version of PHP it was built against and a
copy of the library needed to run it. Occasionally a build can fail, and
that also applies to extension builds in the CVS branches. Nobody's
perfect, and all four branches are under some form of active development,
ranging from 'bug fixes only' to 'bleeding-edge experimental'. So
occasionally you might get the situation where you need to go back to
snaps and start over because an extension doesn't work (making sure that
the
extension author knows about the bug and has fixed it first, of course).
But it's relatively rare for that to happen with the core extensions,
because build problems are usually reported quite quickly.You need to pick up the most recent copy of PHP 5_1 branch from the snaps
box if you're planning to load other extensions alongside PHP, as it says
in
my INSTALL.txt, and if php-gtk2.dll won't load I'll need to know about it
so
I can rebuild PHP-GTK 2 against that version and put a working version on
the site. In fact I just now tested it, and it doesn't load, because
there was an API bump on 22nd September that I wasn't aware of. That was
the problem I needed to know about, and it means I need to build a new
version of php-gtk2.dll against the CVS version of PHP 5.1-dev so that you
can use it with the latest snaps. I'll mail the list as soon as I've made
that version live, but it'll probably be some time tomorrow.When we have an official PHP 5.1 release, it will become much easier to
deal
with all this - you'll be able to use www.php.net for the PHP and
extensions
download, and I'll build against that edition. But RC 1 is not an
official release, and the fact that this particular one hasn't been
followed
by further release candidates in the space of two months says it wasn't
anywhere near stable enough for release material. In fact Zeev tried to
roll
RC 2 in mid-September and found it still wasn't ready, so didn't go ahead
with that plan. That being the situation, we absolutely need to rely on
the
snaps builds for now, for any form of win32 distribution.BTW, Edin just made it easier to pick up the correct individual PECL
extension for the branch you're using - take a look at
http://pecl4win.php.net/branch.php. He also (now) links to the relevant
list
on that site, from the snaps site, so nobody needs to download a big
zipfile
to get a single PECL extension any more.Hope that makes everything a bit clearer,
- Steph
----- Original Message -----
From: "Joshua Seward" jseward@columbus.rr.com
To: "PHP DEV" php-gtk-dev@lists.php.net
Sent: Saturday, October 01, 2005 7:49 AM
Subject: [PHP-GTK-DEV] PHP-GTK2 mysql Extensions?Problem Solved!
After getting sleep, I smacked myself for doing everything backwards.
The only extensions that would load with the php-gtk2.dll are the ones
from
the main php.net site.I tried this on the 8000 time. Please stop sending people to the snapshot
website. They are not the correct build.I guarantee this!!!!!!
There is a fault in the php_mysqli.dll though. Windows command crashes
every
time php-gtk2 tries to load it.The php_mysql.dll and other work fine.
Sorry for all the bad e-mails before and thank you all for your time and
patience.Thanks Again,
Josh
This has NOT been the policy. The person who came up with
this stupid idea should be punis..informed about it.
There's this nice download-server running thttpd (IIRC)
somewhere where the RCs and such USED to be put.
(dejavu or did I actually mention about this earlier? :)
--Jani
--
Give me your money at @ http://pecl.php.net/wishlist.php/sniper
Donating money may make me happier and friendlier for a limited period!
Death to all 4 letter abbreviations starting with P!
Guys,
You don't need to read the whole of the history below, but doing so might
help to illustrate some of the confusion caused by distributing PHP release
candidates and extension packs on the php.net downloads page alongside the
official PHP releases.Can we re-think this policy, please?
My own feeling is that RCs shouldn't be announced in this way, but I know
you all want a broad test base for them.Perhaps we could make them available via a separate download page with a
header and text making it fully clear these are not PHP releases?
- Steph
I thought it was only me and Zeev that didn't like it :)
So can we make a policy over this and write it in stone somewhere?
Or do we have to write it in water?
ps your new 'limited period' sig is rather wonderful...
----- Original Message -----
From: "Jani Taskinen" sniper@iki.fi
To: "Steph" steph@zend.com
Cc: "internals" internals@lists.php.net
Sent: Sunday, October 02, 2005 12:45 AM
Subject: Re: [PHP-DEV] Fw: [PHP-GTK-DEV] PHP-GTK2 mysql Extensions?
This has NOT been the policy. The person who came up with this stupid idea should be punis..informed about it. There's this nice download-server running thttpd (IIRC) somewhere where the RCs and such USED to be put. (dejavu or did I actually mention about this earlier? :) --Jani
--
Give me your money at @ http://pecl.php.net/wishlist.php/sniper
Donating money may make me happier and friendlier for a limited period!
Death to all 4 letter abbreviations starting with P!Guys,
You don't need to read the whole of the history below, but doing so
might
help to illustrate some of the confusion caused by distributing PHP
release
candidates and extension packs on the php.net downloads page alongside
the
official PHP releases.Can we re-think this policy, please?
My own feeling is that RCs shouldn't be announced in this way, but I
know
you all want a broad test base for them.Perhaps we could make them available via a separate download page with a
header and text making it fully clear these are not PHP releases?
- Steph