Re: how to deal with php5 only packages (was: [PEPr] Comment on Networking::GeoIP)

David Costa wrote: > >On Jun 16, 2004, at 6:36 PM, Bertrand Mansion wrote: >> >snip >> >> #pear install Package_Using_Sqlite >> >> --> Aaaaah ! >> >> You have installed both packages MANUALLY ! :-o >> >In your dreams may be ;) If you run on PHP4 you need to add the >sqlite.so extension and pray. Many people reported problem with this >on Mac OS X >semi-official build by entropy >http://www.entropy.ch/phpbb2/viewtopic.php?t=782&highlight=sqlite > >and btw you can't do pear install sqlite AFAIK remember it is a PECL >module so you need pear download sqlite and pear bundle sqlite and then >install. Even if you do it with >pear install only you will still need to mess with config files, >restart apache etc. Sqlite is running fine here on Panther with PHP 4.3 : # phpize # ./configure --with-sqlite # make install Even dl() is working now, without dlcompat. Anyway, what you describe seems to be a Mac related problem. >> Looks to me like Sqlite is not a valid reason to go PHP5 only :) > >Well, what would be a valid reason ? To me, the benefit of using a >superior object model is a valid reason alone, excluding SQLite. To be a "superior" object model, it has to be used correctly. If people start making all their variables public, I don't see what's superior. If people do not understand why they should use protected, that's a problem too. >> Furthermore, in your own mp3 package, I don't really see a reason why >> you use Sqlite. Well, that's just me, no need to argue here... > >No problem, just I think for a simple thing like a playlist backup >SQlite would work much better then anything else. e.g. imagine you >would want to send me a list >of your song in a db via email.... As you said before, sqlite is typeless. Now guess how much space it has to take in your db file to store an integer ? And for a string ? Soon you will realize that a mysql DB file can be a lot smaller than a sqlite DB file, even when they contain the same data :) Still, sqlite portability is a nice feature. But CSV are portables too :) >Again we have different views. I think that I need a valid reason to >write something for PHP 4 with 5.0.0-dev already out and used, not the >other way around ;) Probably you have. But using sqlite was not one of them. >Of course I am well aware of the initial limitations. A PHP 5 only >package will not be, at least for now, as widely used as a PHP 4 >package and it will not be able to roll a stable >release for a while. Indeed. Bertrand Mansion Mamasam