Re: CMSystem written in PHP

On Sun, 2002-12-01 at 20:46, Arnaud Limbourg wrote: > > While I agree, we may want to rename it from the PHP Extension and > > APPLICATION Repository then. :) > > Ahh, you're raising an old point here :) > > We could say that pear means nothing, just a fruit name, we wouldn't have any problem ;) I want PEAR to support applications at one point, but there's a lot of work to do in the installer until that can become a reality. The idea is to integrate the installer with web servers (starting with Apache) so when you install for example "PEAR_Forum", it configures a destination for it in your Apache config, and so on. A new file role, "htdoc", will be used for this. But like I said, a lot of work remains before it makes any sense in having anything else than command-line applications (like PhpDocumentor) in PEAR. > > That having been said I have three comments: > > > > 1) making your CMS available in PEAR package format may make > > installation easier for your users. > > That's one of the points of the installer. Any application can use the pear installer ;) > > > 2) Perhaps there are components of your CMS that would be appropriate > > for PEAR (I haven't looked) > > Indeed, PEAR cannot accept entire application or even frameworks (like binarycloud); not > because they're not acceptable but because such is not the aim of PEAR. However, as you say > they can, and should do so if they want, use PEAR classes. (btw i'm not addressing to george > here, just making a general statement ;)) > > > 3) GPL'd software in PEAR kinda sucks. > > This point is under clarification, hey stig ?? :) Until we have a response from RMS on how to interpret the GPL license on this, we can't accept GPL stuff in PEAR. - Stig