Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95809
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain honestempire.com designates 66.111.4.28 as permitted sender)
Message-ID: <1473360319.82408.719912961.2D1C65E2@webmail.messagingengine.com>
To: internals@lists.php.net
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
Date: Thu, 08 Sep 2016 19:45:19 +0100
In-Reply-To: <3ec68c67-a4de-1727-c3c8-e8fcacd95f0c@lsces.co.uk>
References: <CANaX5nf5S6aS-ZaB=51qvXv+wbReGb2petPBDogTA+MNMHyysQ@mail.gmail.com>
 <04998da0-6344-0b8b-c69a-411400e340ba@lsces.co.uk>
 <1473323097.1378681.719308017.2139F909@webmail.messagingengine.com>
 <8493a9dd-1f0e-f15f-3651-0278cf25234b@lsces.co.uk>
 <ec690b39-00d3-b2f7-60e7-5dd5b30cd7b3@gmx.de>
 <e8584697-8efe-e933-ca74-a404c92c30ec@lsces.co.uk>
 <CANUQDCgfcFtTOmKYj0osvsOwVOi2Y3SkAXGFyVdsFh0-UR04aA@mail.gmail.com>
 <bac1fc14-99bf-fc2e-39ce-a1662092785d@lsces.co.uk>
 <CADMz3weWurQpusUSkCx=25c6fxuWArSzQaedr4HnGVrLc11PzQ@mail.gmail.com>
 <3ec68c67-a4de-1727-c3c8-e8fcacd95f0c@lsces.co.uk>
Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace withcomposer/pickle
From: daniel@honestempire.com (Daniel Morris)

On Thu, 8 Sep 2016, at 05:21 PM, Lester Caine wrote:
> Another couple of hours wasted, but I understand where things are now,
> and basically the simple fact is that composer global mode is nothing of
> the sort. The PHP_CodeSniffer composer install does not work and I
> understand NOW why the Smarty one also failed. I was expecting the files
> to be available to the nginx server but they were hidden away in my home
> directory. I still have to work out just how to reset things to move the
> code to /usr/shared/phpx/composer to parallel the PEAR version.

PHP_CodeSniffer should not be run by the web server, it's a command-line
development tool, it should be run by the developer, or as part of a
build (e.g. Travis, Ant, etcetera)

Composer allows you to separate the dependencies, for example, in your
case; Smarty is a production and development dependency, and PHPCS is a
development dependency only, your `composer.json` should have  something
similar to the following:

```
{
    "require": {
        "smarty/smarty": "~3.1"
    },
    "require-dev": {
        "squizlabs/php_codesniffer": "^2.7"
    }
}
```

That way, anytime someone runs `composer install` from your project
directory (or wherever the composer.json dependency is contained), it
will create a `vendor` directory with your dependencies, if you haven't
used the `--no-dev` flag when running `composer install`, you will have
PHPCS ready and waiting in `vendor/bin`, others will have the same
toolset you're using, so discrepancies between environments will have
been reduced.

--
Daniel Morris
daniel@honestempire.com