Rasmus Lerdorf wrote:
On Tue, 24 Jun 2003, Hartmut Holzgraefe wrote:
Gareth Ardron wrote:
Walk through menu of "do you want X enabled? do you want Y enabled?" which
just stores as a string and excecutes `./configure {string value}`
do you remember the linux kernel times *before* we had menuconfig
At 02:45 25/06/2003, Rasmus Lerdorf wrote:
On Tue, 24 Jun 2003, Edin Kadribasic wrote:
> > At 04:32 PM 6/24/2003 +0200, Sascha Schumann wrote:
> > > SQLite should become as pervasive as the session extension.
> > > It is really a killer feature.
> >
> > I think this was well put. It seems t
On Wed, 25 Jun 2003, Marcus Börger wrote:
> RL> On Tue, 24 Jun 2003, Edin Kadribasic wrote:
> >> > At 04:32 PM 6/24/2003 +0200, Sascha Schumann wrote:
> >> > > SQLite should become as pervasive as the session extension.
> >> > > It is really a killer feature.
> >> >
> >> > I think this was
Hello Rasmus,
Wednesday, June 25, 2003, 1:45:48 AM, you wrote:
RL> On Tue, 24 Jun 2003, Edin Kadribasic wrote:
>> > At 04:32 PM 6/24/2003 +0200, Sascha Schumann wrote:
>> > > SQLite should become as pervasive as the session extension.
>> > > It is really a killer feature.
>> >
>> > I thin
On Tue, 24 Jun 2003, Edin Kadribasic wrote:
> > At 04:32 PM 6/24/2003 +0200, Sascha Schumann wrote:
> > > SQLite should become as pervasive as the session extension.
> > > It is really a killer feature.
> >
> > I think this was well put. It seems there is "almost" a consensus that
> > bundl
> At 04:32 PM 6/24/2003 +0200, Sascha Schumann wrote:
> > SQLite should become as pervasive as the session extension.
> > It is really a killer feature.
>
> I think this was well put. It seems there is "almost" a consensus that
> bundling and enabling sqlite by default is a big advantage fo
At 04:32 PM 6/24/2003 +0200, Sascha Schumann wrote:
SQLite should become as pervasive as the session extension.
It is really a killer feature.
I think this was well put. It seems there is "almost" a consensus that
bundling and enabling sqlite by default is a big advantage for PHP and its
On Tuesday 24 June 2003 7:42 pm, Marco Tabini wrote:
>
> - How many "kernel people" do we know anyway? The majority of PHP users
> are not kernel people (or whatever the equivalent for PHP is). I, for
> one, recompile my kernel rather frequently and enjoy using the
> menu-based tools; and I know l
> I don't know a single kernel guy who uses the graphical interfaces. And
> like Zeev said, we used to have this fancy configuration tool. It even
> had a web interface for a while where you could go and click on checkboxes
> and it would generate your configuration. It was actually pretty good,
After long amounts of reading
+1
However, I'd like to see sqlite remain in PECL, and start using PECL the
way it should be. That would be a good start. I think it would ease
some minds, and point out whatever areas happen to still be *real*
issues (if any).
Shane
--
PHP Internals - PHP Runti
I don't think the question is bundling SQLite, as many of us really don't
seem to mind that. Even I who am notorious for not liking bundling
software won't argue with this one. I see it as a Good Thing for PHP as a
whole. I'm not sure that it should be enabled by default though, which is
an enti
Yes, Rasmus hit the nail on the button!
> So yes, while I agree with the general sentiment of moving more stuff to
> PECL, for fundamental things like PCRE, Session and now SQL-access to flat
> files, that make up the core of what makes PHP what it is, I think this
> should be bundled.
The two
Yeah, I was surprised to see it on the 4_3 branch as well. I don't think
it should be there.
I would like to suggest a 4.4 release at some point after we get 4.3.3 out
the door with the aim being to bridge users from 4.x to 5.x. It would
look as much like 5.x as is feasible, but be based on the
On Tue, 24 Jun 2003, Hartmut Holzgraefe wrote:
> Gareth Ardron wrote:
> > For those of you who have seen the debconf stuff, how about something like
> > that?
> >
> > Walk through menu of "do you want X enabled? do you want Y enabled?" which
> > just stores as a string and excecutes `./configure {s
Nevermind, I was just wondering about the PHP_4_3 branch
having it too, but that's propably just temporary thing.
--Jani
On Tue, 24 Jun 2003, Jani Taskinen wrote:
>
>Where/when it was decided to be included in the main
>distribution in the first place?
>
>--
Where/when it was decided to be included in the main
distribution in the first place?
--Jani
On 22 Jun 2003, Sterling Hughes wrote:
>Hey,
>
>Unless anyone objects I'm going to enable the sqlite extension by
>default for PHP5. The extension comes with the bundled sqlite lib
Gareth Ardron wrote:
For those of you who have seen the debconf stuff, how about something like
that?
Walk through menu of "do you want X enabled? do you want Y enabled?" which
just stores as a string and excecutes `./configure {string value}`
do you remember the linux kernel times *before* we h
On Tuesday 24 June 2003 3:51 pm, Dan Kalowsky wrote:
> I've proposed such solutions in the past, and only recently have come to
> dislike the means (but not the idea). Mainly because the mechanism to do
> such a configuration could lead to a longer configuration time then
> compile time.
For thos
On June 24, 2003 10:50 am, George Schlossnagle wrote:
> I'm not approaching this from a performance standpoint, but from one
> where statically compiled extensions slow the overall release process,
> make it difficult for users to incrementally upgrade their extensions,
> and generally contribute t
Menu driven approach is much slower then the ./configure approach and only
makes sense when you have a mind numbingly large number options like you do
in the Linux kernel. The default packages are the for the average user there
is nothing to say advanced users who have no need to sqlite or anyth
One of the main reasons PHP has reached the popularity it has today is
because it was mindnumbingly easy to get started with it and you could do
so many things with a default PHP installation. You can't twirl a wet cat
without hitting servers with Gallery, PHP-Nuke, PHPBB or one of the other
dozen
At 17:46 24/06/2003, Marco Tabini wrote:
Why not disable all extensions by default and add a configuration
utility that is launched before compilation--sort-of like the Linux
kernel?
We had one of those once, it was so popular that nobody even said anything
when we removed it :)
Zeev
--
PHP Inte
At 17:50 24/06/2003, George Schlossnagle wrote:
On Tuesday, June 24, 2003, at 10:56 AM, Ilia A. wrote:
On June 24, 2003 10:40 am, George Schlossnagle wrote:
I dig including it in ext, and bundling the full sqlite sources as
well. I just don't think it should be enabled by default.
Enabling sqlit
Even with a menu-driven approach (e.g.: make menuconfig in the kernel)?
My thought is that you'd still feed the end result through ./configure,
but the app would make it somewhat easier for those who don't have a
clue. It would also be possible to distribute "pre-packaged"
configurations for common
I've proposed such solutions in the past, and only recently have come to
dislike the means (but not the idea). Mainly because the mechanism to do
such a configuration could lead to a longer configuration time then
compile time.
On Tue, 24 Jun 2003, Marco Tabini wrote:
> Why not disable all ext
Why not disable all extensions by default and add a configuration
utility that is launched before compilation--sort-of like the Linux
kernel?
Marco
On Tue, 2003-06-24 at 10:56, Ilia A. wrote:
> On June 24, 2003 10:40 am, George Schlossnagle wrote:
> > I dig including it in ext, and bundling the
On Tuesday, June 24, 2003, at 10:56 AM, Ilia A. wrote:
On June 24, 2003 10:40 am, George Schlossnagle wrote:
I dig including it in ext, and bundling the full sqlite sources as
well. I just don't think it should be enabled by default.
Enabling sqlite by default has virtually no performance impact
On June 24, 2003 10:40 am, George Schlossnagle wrote:
> I dig including it in ext, and bundling the full sqlite sources as
> well. I just don't think it should be enabled by default.
Enabling sqlite by default has virtually no performance impact. Your binary is
increased by roughly 100k and you
On Tuesday, June 24, 2003, at 10:24 AM, Wez Furlong wrote:
Sterling has a good point that sqlite is something that could really
boost
PHP. Currently, the only way to ensure that it is a standard feature
is to
enable it by default. Sad but true.
That is true. It's something of a chicken and e
SQLite should become as pervasive as the session extension.
It is really a killer feature.
- Sascha
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Sterling has a good point that sqlite is something that could really boost
PHP. Currently, the only way to ensure that it is a standard feature is to
enable it by default. Sad but true.
My main misgiving with it being enabled by default is that it will make it
harder for me to publish releases o
On June 23, 2003 01:48 pm, Dan Kalowsky wrote:
> As always I'm against any enable by default thinking.
> Why, oh why, are we making this wonderful configure script
> completely useless?
In a perfect world nothing would be enabled by default and each user would
enable just the extensions they wont
On Tue, 24 Jun 2003 10:03:51 -0400
George Schlossnagle <[EMAIL PROTECTED]> wrote:
> This is a good synopsis of some of my feelings. PECL == Siberia is a
> recurrent gripe, but anytime someone works on a cool project they want
>
> it to bundle, ship and be enabled by default instead of promoting
On Tuesday, June 24, 2003, at 09:56 AM, Philip Olson wrote:
This is a wonderful time to promote
PEAR and the PECL situation rather than force featured
bundles on people, like sqlite.
This is a good synopsis of some of my feelings. PECL == Siberia is a
recurrent gripe, but anytime someone works o
-1
People that want to use sqlite can download the source,
they can even use the pear command to do this either by:
a) pear install sqlite (to create the .so)
extension=sqlite.so
b) pear bundle sqlite (to download the source)
./configure --with-sqlite
Forcing the entire world
Hello Sterling,
Monday, June 23, 2003, 4:38:42 AM, you wrote:
SH> Hey,
SH> Unless anyone objects I'm going to enable the sqlite extension by
SH> default for PHP5. The extension comes with the bundled sqlite library
SH> which is 1.5mb in total (cd ext/sqlite/libsqlite/src/; du -ch *.c *.h),
SH>
-1
As always I'm against any enable by default thinking.
Why, oh why, are we making this wonderful configure script
completely useless?
On Sun, 22 Jun 2003, Sterling Hughes wrote:
> Hey,
>
> Unless anyone objects I'm going to enable the sqlite extension by
> default for PHP5. The extension c
nope, just in cvs. and just as of last night. :) But the footprint of
php5 is actually smaller with regards to sqlite, as the client library
caused more download time.
-Sterling
On Mon, 2003-06-23 at 13:58, Andi Gutmans wrote:
> At 01:12 AM 6/23/2003 -0400, Sterling Hughes wrote:
> >1.5 mb is t
At 01:12 AM 6/23/2003 -0400, Sterling Hughes wrote:
1.5 mb is tiny :)
1.5 mb is just a du -ch *.c *.h, and its a one time download. Then you
cvs upd the rest of the changes as they happen. As a point of
reference, the mbstring extension is 2.9 mb of data, sqlite is in total
1.9 mb of data.
Libm
On Mon, 2003-06-23 at 03:55, Thies C. Arntzen wrote:
> On Sun, Jun 22, 2003 at 10:38:42PM -0400, Sterling Hughes wrote:
> > Hey,
> >
> > Unless anyone objects I'm going to enable the sqlite extension by
>
> i object strongly. sterling, why have you gotten into the
> enable-all, bundle-all
I think it's a good idea.
Zeev
At 05:38 23/06/2003, Sterling Hughes wrote:
Hey,
Unless anyone objects I'm going to enable the sqlite extension by
default for PHP5. The extension comes with the bundled sqlite library
which is 1.5mb in total (cd ext/sqlite/libsqlite/src/; du -ch *.c *.h),
and is
On Mon, 2003-06-23 at 04:38, Sterling Hughes wrote:
> Unless anyone objects I'm going to enable the sqlite extension by
> default for PHP5. The extension comes with the bundled sqlite library
> which is 1.5mb in total (cd ext/sqlite/libsqlite/src/; du -ch *.c *.h),
> and is a good alternative to u
On Mon, 22 Jun 2003, Sterling Hughes wrote:
> Unless anyone objects I'm going to enable the sqlite extension by
> default for PHP5. The extension comes with the bundled sqlite library
> which is 1.5mb in total (cd ext/sqlite/libsqlite/src/; du -ch *.c *.h),
> and is a good alternative to using My
When I bundled the library, I only included the required files (the
official distro is a bit larger than what we include in ext/sqlite).
--Wez.
On Mon, 23 Jun 2003, Andi Gutmans wrote:
> On one hand I think having 1.5MB in our release tree is quite a lot (can
> anything be removed)? On the other
On Sun, Jun 22, 2003 at 10:38:42PM -0400, Sterling Hughes wrote:
> Hey,
>
> Unless anyone objects I'm going to enable the sqlite extension by
i object strongly. sterling, why have you gotten into the
enable-all, bundle-all mode lately? what do you gain?
thies
--
PHP Internals - PHP
On Sun, 22 Jun 2003, George Schlossnagle wrote:
> We should add
>
> --without-kitchen-sink
>
> to disable all these new bundled extensions.
--disable-all is what you have for that
Derick
--
"Interpreting what the GPL actually means is a job best left to those
that read th
Sterling Hughes wrote:
> As I mentioned its been bundled for quite awhile now. :)
But only hours ago it was symlinked from PECL to php5 :)
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/
http://www.professionelle-softwareentwicklung-m
1.5 mb is tiny :)
1.5 mb is just a du -ch *.c *.h, and its a one time download. Then you
cvs upd the rest of the changes as they happen. As a point of
reference, the mbstring extension is 2.9 mb of data, sqlite is in total
1.9 mb of data.
Libmysql was much more code than the bundled sqlite is.
At 01:01 AM 6/23/2003 -0400, Sterling Hughes wrote:
Well, its actually already bundled. If you've cvs updated then you have
SQLite already bundled. SQLite is in PECL, and the PECL version bundles
the library. 1.5 mb is tiny :)
I think it's probably time to update makedist so that it also brings
On Mon, 2003-06-23 at 02:03, Andi Gutmans wrote:
> At 10:38 PM 6/22/2003 -0400, Sterling Hughes wrote:
> >Hey,
> >
> >Unless anyone objects I'm going to enable the sqlite extension by
> >default for PHP5. The extension comes with the bundled sqlite library
> >which is 1.5mb in total (cd ext/sqlite
On Sun, 2003-06-22 at 23:52, George Schlossnagle wrote:
> On Sunday, June 22, 2003, at 11:39 PM, Sterling Hughes wrote:
>
> > --disable-all you mean?
>
> Well, certain extension (curl, openssl) are almost necessary for the
> language itself to be fully functional, whereas sqlite is just a db
>
At 10:38 PM 6/22/2003 -0400, Sterling Hughes wrote:
Hey,
Unless anyone objects I'm going to enable the sqlite extension by
default for PHP5. The extension comes with the bundled sqlite library
which is 1.5mb in total (cd ext/sqlite/libsqlite/src/; du -ch *.c *.h),
and is a good alternative to usi
On Sunday, June 22, 2003, at 11:39 PM, Sterling Hughes wrote:
--disable-all you mean?
Well, certain extension (curl, openssl) are almost necessary for the
language itself to be fully functional, whereas sqlite is just a db
extension. It being present at compile time doesn't alter the way the
--disable-all you mean?
-Sterling
On Sun, 2003-06-22 at 23:47, George Schlossnagle wrote:
> On Sunday, June 22, 2003, at 10:38 PM, Sterling Hughes wrote:
>
> > Hey,
> >
> > Unless anyone objects I'm going to enable the sqlite extension by
> > default for PHP5. The extension comes with the bund
On Sunday, June 22, 2003, at 10:38 PM, Sterling Hughes wrote:
Hey,
Unless anyone objects I'm going to enable the sqlite extension by
default for PHP5. The extension comes with the bundled sqlite library
which is 1.5mb in total (cd ext/sqlite/libsqlite/src/; du -ch *.c *.h),
and is a good altern
55 matches
Mail list logo
