Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95792 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 37189 invoked from network); 8 Sep 2016 12:26:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Sep 2016 12:26:43 -0000 Authentication-Results: pb1.pair.com smtp.mail=me@kelunik.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=me@kelunik.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain kelunik.com from 81.169.146.216 cause and error) X-PHP-List-Original-Sender: me@kelunik.com X-Host-Fingerprint: 81.169.146.216 mo4-p00-ob.smtp.rzone.de Received: from [81.169.146.216] ([81.169.146.216:23290] helo=mo4-p00-ob.smtp.rzone.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6F/69-36123-00951D75 for ; Thu, 08 Sep 2016 08:26:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1473337597; l=8866; s=domk; d=kelunik.com; h=Content-Type:Cc:To:Subject:Date:From:References:In-Reply-To: MIME-Version; bh=Od3bH+lRQqNhX11B/TymfDB3Axs/Ex1CjQeNU72h/LE=; b=l4fv85MBT6o//gmm+9vnI6Uswy1O8x7MIFBA6rGfkGvhq9dKOoRxIeIWJ0/U/I+MaHl CgwRvSYE5Sbo6e/9qB2e/CLdi6b5tdc8tSBv80E/q/1hPrM5V0q35UjvL02tSAvkWM1go WD06WimRxPckYx/BPUJy8unSPJfIp4dDYWU= X-RZG-AUTH: :IWkkfkWkbvHsXQGmRYmUo9mls2vWuiu+7SLGvomb4bl9EfHtO3I6 X-RZG-CLASS-ID: mo00 Received: from mail-wm0-f41.google.com ([74.125.82.41]) by smtp.strato.de (RZmta 39.1 AUTH) with ESMTPSA id 90923bs88CQbAFq (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp384r1 with 384 ECDH bits, eq. 7680 bits RSA)) (Client did not present a certificate) for ; Thu, 8 Sep 2016 14:26:37 +0200 (CEST) Received: by mail-wm0-f41.google.com with SMTP id w12so85949959wmf.0 for ; Thu, 08 Sep 2016 05:26:37 -0700 (PDT) X-Gm-Message-State: AE9vXwNT1MARav00ctetsi9oTRXbl7IPECDx9Kgo0pG2JriFP8tR8JLLkKjLgWQZk1DWEPjvyqp8S5vyBwmZeQ== X-Received: by 10.194.117.33 with SMTP id kb1mr35974367wjb.79.1473337597033; Thu, 08 Sep 2016 05:26:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.180.7 with HTTP; Thu, 8 Sep 2016 05:26:35 -0700 (PDT) In-Reply-To: References: <04998da0-6344-0b8b-c69a-411400e340ba@lsces.co.uk> <1473323097.1378681.719308017.2139F909@webmail.messagingengine.com> <8493a9dd-1f0e-f15f-3651-0278cf25234b@lsces.co.uk> Date: Thu, 8 Sep 2016 14:26:35 +0200 X-Gmail-Original-Message-ID: Message-ID: To: Lester Caine Cc: PHP Internals Content-Type: multipart/alternative; boundary=001a1130caa21b12f1053bfe2414 Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace withcomposer/pickle From: me@kelunik.com (Niklas Keller) --001a1130caa21b12f1053bfe2414 Content-Type: text/plain; charset=UTF-8 2016-09-08 14:13 GMT+02:00 Lester Caine : > On 08/09/16 12:33, Christoph M. Becker wrote: > > On 08.09.2016 at 12:35, Lester Caine wrote: > > > >> On 08/09/16 09:24, Daniel Morris wrote: > >>> On Thu, 8 Sep 2016, at 09:07 AM, Lester Caine wrote: > >>>> 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? > >>> > >>> PHP_CodeSniffer is already compatible with Composer, and Composer has > >>> the ability to specify dependencies, and dependencies intended for > >>> development. After running composer install you can execute > >>> `vendor/bin/phpcs`, and if you were working collaboratively, > >>> collaborators would all have the same toolset that you have. > >> > >> I know this is a problem for PHP_CodeSniffer to rework it's > >> documentation, > > > > The docs seem to be fine: > > . > > > >> but it is a chicken and egg. PEAR provides a framework to > >> store things like PHP_CodeSniffer in the common area away from our web > >> folders. A similar set of guidelines to install via composer are needed > >> as an alternative and those are not currently in place? > > > > The `global` command appears to solve that: > > . > > That is the chicken ... if you ARE already composer user then it will > make some sense, but pear gives a phpcs -h which works out of the box. > ./vendor/bin/phpcs -h does not sound right as an alternative? Why does it seem not right? It's perfectly right and the way to go if you're using Composer. An alternative would be to use Composer's global require and adding the global "bin" directory of Composer to your PATH variable. > And I > would expect different installations of composer will affect that > installation? > What do you mean by "affect that installation"? Regards, Niklas > I have no doubt that composer can be made to work. The question here is > if that is as easy to achieve as simply keeping PEAR installer as the > fall back process? Certainly when I last tried to set up composer I ran > into difficulty because I have 4 versions of PHP active. Something which > pear seems to cope with without a problem. > > -- > 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 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --001a1130caa21b12f1053bfe2414--