RE: [PHP-DEV] enabling postgresql by default
| From: | Tim Parkin | Date: | Tue, 24 Jun 2003 21:28:34 +0000 |
| Subject: | RE: [PHP-DEV] enabling postgresql by default | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-2747@lists.php.net to get a copy of this message | ||
On Tue, 24 Jun 2003, Tim Parkin wrote:
>> Could you please point me to the recent discussion that takes into
>> account the progress of Postgres and the change in licensing of MySQL
>
>There isn't a discussion on that topic per say, but there are plenty on
>why we do(n't) want to bundle new options with the code. Please read
>those and bash them into place for this drawing board.
Perhaps the conversation has more pertinence in the current light? I
have read many
posts about default bundling and agree with many. However, some things
get bundled,
some others do not.
I agree with Rasmus and Sterling regarding SQLite. I also agree
than unbundling mysql is a good idea in the present circumstance
(whereas previously
there was no reason). It doesn't seem a cut-and-dried situation.
I would just like to know what the arguments regarding the bundling of
postgres are.
If they've been posted before then I'll read them.
> That discussion is mostly non public and will not become public until
we can
> find a consensus/solution togeter with MySQL on LinuxTag during july.
Sorry, it appeared from what Zeev had said that this was a matter of
historical record.
Tim
----------------------------------------------
Tim Parkin
Managing Director
Pollenation Internet Ltd
www.pollenation.net
m : 07980 59 47 68
t : 01132 25 25 00