Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:16105 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 42648 invoked by uid 1010); 27 Apr 2005 00:01:39 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 42633 invoked by uid 1007); 27 Apr 2005 00:01:39 -0000 Message-ID: <20050427000139.42632.qmail@lists.php.net> To: internals@lists.php.net Date: Wed, 27 Apr 2005 02:01:39 +0200 User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 References: <426EAC2F.3060401@php.net> In-Reply-To: <426EAC2F.3060401@php.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 80.137.12.81 Subject: Re: pear package in 4.3.x releases From: akorthaus@web.de (Andreas Korthaus) Greg Beaver wrote: >> Was the removal of most pear package in 4.3.11 intentional? > > Yes. > Has this been announced somewhere? I did not see anything in ChangeLog and release notes. > The only other change being considered for the future would be to > make it easier to install PEAR by providing a single file containing all > resources, but this is still very much on the drawing board, and would > not affect the packages ultimately installed. If you have a shell-account and you are superuser, it is not difficult to install pear/packages. If you are not superuser, it becomes more difficult. But if you don't have a shell-account installation becomes really hard. go-pear for web does not work 100%, same for web-installer. Some people cannot use it at all, because it simply does not work. So often your only option is to install pear/packages by uploading the extracted php-files from your PC. > The plan is to rely on users installing these packages. It was becoming > increasingly difficult to maintain the bundles, and because older > versions were often bundled, it introduced potential security risks as > well. One of the biggest problems of pear is, that most people simply cannot use it! If I recommend people using pear-package XY, in 4 of 5 cases the user could not use the package because it is not installed, and he has no idea how to get it work. I know it is possible, but if you install it the first time it could become really hard. If you want to rely on users to install packages (which is a good idea IMHO) all users (not only superusers) need a reliable tool for installation/management (also without shell-account). best regards Andreas