RE: [PEAR] Suggestions regarding Pear & PHP5

Hi Joshua, Joshua Eichorn wrote: > What sort of dependency documentation are you thinking of, add tags to > docblock saying what packages a class (etc) uses, or something based > on inheirtance (and in 5 implements) trees. Well, finding what packages and external code it needs is not so hard, just to look at in the code and see what they include/require. Having a list, as for each Pear package makes it much easier though. What I find more difficult to find out though is what PHP/Zend needs to support to function properly with that package. In some cases it's easy to find out. A package for webmail normally needs imap-support compiled in. What's much harder to find out though is the not so obvious features needed in the server (both the server application such as Apache or external applications on the server, such as wv for viewing Word documents, and in PHP. It's the same regarding settings for the php.ini. For example, I spended days trying to get TUTOS (www.tutos.org) to work. My problem was that when I tried to initialize the database, I just got garbage on the screen. Finally, after several post on the TUTOS forum, the solution was found. I hade to change a setting in php.ini and it worked perfectly. My main reasons for wanting to know this is: - Have as slim server as possible. That is not having any software or compiled in support of features I don't need. - Security. The less of the above, the more secure it will be. I believe it would be possible to save a lot of time, and also get a better performance of the server, if this information was more available. I would just need to check how my server is configured, that I have the needed support compiled in and that my config files is correct. Now I have most of the stuff compiled in (at least on my dev server) and it just feels bloated with performance consuming (most importantly RAM using) features that is not needed. I can understand that for many it wont be very easy to know exactly what needs to be done in php.ini. I know for me it wont be for the things I develop, but luckily my stuff will not be public. At least not yet. So, basically what I want to accomplish with this is to save myself lots of time. Time which I instead can focus on more important issues, such as coding (or my girlfriend). Kind regards, /Thomas