Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95771 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 65958 invoked from network); 8 Sep 2016 08:07:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Sep 2016 08:07:11 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:52099] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 72/91-36123-B2C11D75 for ; Thu, 08 Sep 2016 04:07:08 -0400 Received: (qmail 9401 invoked by uid 89); 8 Sep 2016 08:07:04 -0000 Received: by simscan 1.3.1 ppid: 9384, pid: 9391, t: 3.8535s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.7?) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 8 Sep 2016 08:07:00 -0000 To: internals@lists.php.net References: Message-ID: <04998da0-6344-0b8b-c69a-411400e340ba@lsces.co.uk> Date: Thu, 8 Sep 2016 09:07:00 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle From: lester@lsces.co.uk (Lester Caine) On 02/09/16 20:32, Davey Shafik wrote: > I'm also proposing voting choices around the optional/default introduction > of composer/pickle. I've just been through an exercise to give PHP_CodeSniffer a go on my code base. I've not worried too much about that in the past since Eclipse in general flags style problems as well as simple errors. This is a package that SUSE does not support, so the current install path is just PEAR. I don't see packages like this as a library that my sites use. It is a stand alone tool ( and a command line one at that :) ) so how would loading that be managed if PEAR is not available? I had the problem having loaded the tool in finding the rule sets so that I could create one suitable for my own application. That is dictated by SUSE was was not quite where I expected it, so this may also be something that an alternative tool loader might be able to help with? Main reason for loading was to give some of the PSR rule checks a try to see just what affect they would have on the code, but I don't think this approach will help with the structural changes needed? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk