Re: php4/pear proposal, core stuff

> > Maybe just have to consider what is a core lib. Imho, we should consider core > lib all libs can > >be use in most of higher level classes, and work with data > (dates,time,numbers,strings,...), >"low-level" I/O or rfc/standart function > (like crypt). > We already disccussed this stuff last year. The decision was and is to keep > only stuff for the pear installer in php4/pear. I don't remember this decision. If my memory serves me well, the decision was to split pear into two parts: core libraries (sort of like the STL for C++) and the rest. > Do you know, that the pear installer will be able to handle dependencies? When > a package requires a other package, this will be installed too. I know many people consider perl's cpan to be a good example. I don't. Last time I needed was for Report Magic for Analog which needed about 10 other packages to work. When I finally gave up on trying to install packages manually (the dependencies got to difficult to handle), and opted for automatic update, it updated nearly everyting including perl itself. Now, I wasn't very happy about it because it broke a lot of things on my system. It is therefore I think that having a standard class library, as known from most other languages, is a God Thing. Edin